Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2fbe5e8792c111cd1581913a1795bc3b92344088b28573285f2442a840f8dc2

Tx prefix hash: d4a0377cbf7a6241ea52eb8b95e911146b0562ef30cbd3005e9be30551525aa5
Tx public key: 88cc469e30b162cd56a3b7c41a43e8f6975043a7f053f4a8c1509ab2294eec4e
Timestamp: 1749966280 Timestamp [UCT]: 2025-06-15 05:44:40 Age [y:d:h:m:s]: 00:152:07:56:11
Block: 1305332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106647 RingCT/type: yes/0
Extra: 0188cc469e30b162cd56a3b7c41a43e8f6975043a7f053f4a8c1509ab2294eec4e021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3d72a88801a8c23ee55ac689f14d340b32e7ba92dc804cae964f0000ca22013 0.600000000000 1792931 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": 1305342, "vin": [ { "gen": { "height": 1305332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3d72a88801a8c23ee55ac689f14d340b32e7ba92dc804cae964f0000ca22013" } } ], "extra": [ 1, 136, 204, 70, 158, 48, 177, 98, 205, 86, 163, 183, 196, 26, 67, 232, 246, 151, 80, 67, 167, 240, 83, 244, 168, 193, 80, 154, 178, 41, 78, 236, 78, 2, 17, 0, 0, 0, 8, 191, 81, 178, 162, 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