Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ee4f32f7d9f594a80b846b8586bee6f519b05111361d22c565cf146641a1521

Tx prefix hash: 6ab90b44f8ef1d9a40a1aad50e450d26c7e1640ea2a53f57a80ee99201ced67a
Tx public key: 7cc09826b4e97348a42b2082179ffcf1b30fba07bd051049d7a32bdd28c7f6f9
Timestamp: 1764272193 Timestamp [UCT]: 2025-11-27 19:36:33 Age [y:d:h:m:s]: 00:006:07:11:28
Block: 1421471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4502 RingCT/type: yes/0
Extra: 017cc09826b4e97348a42b2082179ffcf1b30fba07bd051049d7a32bdd28c7f6f9021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2384cc6b57069ccfc57b874e997d19ef0d3b1e9ea6000f87ea969e29a561fc3 0.600000000000 1910028 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": 1421481, "vin": [ { "gen": { "height": 1421471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2384cc6b57069ccfc57b874e997d19ef0d3b1e9ea6000f87ea969e29a561fc3" } } ], "extra": [ 1, 124, 192, 152, 38, 180, 233, 115, 72, 164, 43, 32, 130, 23, 159, 252, 241, 179, 15, 186, 7, 189, 5, 16, 73, 215, 163, 43, 221, 40, 199, 246, 249, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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