Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2b83866156299a928bd9749c73edc2966b7170dadbba36d17648adada521464

Tx prefix hash: 32e2725352ce4f70925307e5715f88802ca3f9090d5787c792a501ee8c04cdc6
Tx public key: 59aacf6f05f530b3e9b4ca495e725eeeac6dc40c8b6e3d2706d07be6f922c2d7
Timestamp: 1725905679 Timestamp [UCT]: 2024-09-09 18:14:39 Age [y:d:h:m:s]: 00:200:15:25:12
Block: 1106521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143226 RingCT/type: yes/0
Extra: 0159aacf6f05f530b3e9b4ca495e725eeeac6dc40c8b6e3d2706d07be6f922c2d7021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4914beb07f6f1ee7d6849bf59e7f85e95408541913c588927ef5320958c482dd 0.600000000000 1584120 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": 1106531, "vin": [ { "gen": { "height": 1106521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4914beb07f6f1ee7d6849bf59e7f85e95408541913c588927ef5320958c482dd" } } ], "extra": [ 1, 89, 170, 207, 111, 5, 245, 48, 179, 233, 180, 202, 73, 94, 114, 94, 238, 172, 109, 196, 12, 139, 110, 61, 39, 6, 208, 123, 230, 249, 34, 194, 215, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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