Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f776568a5784d1eb430a9f17d28ea721ebf42e663b5e1bb33f4a835051db1e28

Tx prefix hash: b440234bb1c68c8eae64f0b95e8cf961f68af55f4a5c333fffffc4b5fcf532de
Tx public key: 70f8e2b806d35161e5dbad0f4c8d996d615c797c60b8d8719399f5ec44e87141
Timestamp: 1711722385 Timestamp [UCT]: 2024-03-29 14:26:25 Age [y:d:h:m:s]: 01:018:18:03:43
Block: 988947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274351 RingCT/type: yes/0
Extra: 0170f8e2b806d35161e5dbad0f4c8d996d615c797c60b8d8719399f5ec44e871410211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dec786aed140c1d80385c49991e86b924f3a12f0d78bb30a012736b6031e80ae 0.600000000000 1449238 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 988957, "vin": [ { "gen": { "height": 988947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dec786aed140c1d80385c49991e86b924f3a12f0d78bb30a012736b6031e80ae" } } ], "extra": [ 1, 112, 248, 226, 184, 6, 211, 81, 97, 229, 219, 173, 15, 76, 141, 153, 109, 97, 92, 121, 124, 96, 184, 216, 113, 147, 153, 245, 236, 68, 232, 113, 65, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8