Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97dae95302296bb8e3a3d69cecc7321c4699976e3c7fc797f0f62b0a8beb4e2a

Tx prefix hash: 9c84751b379322d21156a321dc931bfdde4997d5eee510f3a25fcea9beab2a5a
Tx public key: 26efd07906ff68d10c0eec0507c450e296094d343f4c4757c724880e95b7763b
Timestamp: 1750540067 Timestamp [UCT]: 2025-06-21 21:07:47 Age [y:d:h:m:s]: 00:196:18:53:19
Block: 1310009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138572 RingCT/type: yes/0
Extra: 0126efd07906ff68d10c0eec0507c450e296094d343f4c4757c724880e95b7763b02110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5252e010fceff656a988ef5783bc15b4c21b48273989a5f66e2c95b8ae6a28f9 0.600000000000 1797626 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": 1310019, "vin": [ { "gen": { "height": 1310009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5252e010fceff656a988ef5783bc15b4c21b48273989a5f66e2c95b8ae6a28f9" } } ], "extra": [ 1, 38, 239, 208, 121, 6, 255, 104, 209, 12, 14, 236, 5, 7, 196, 80, 226, 150, 9, 77, 52, 63, 76, 71, 87, 199, 36, 136, 14, 149, 183, 118, 59, 2, 17, 0, 0, 0, 4, 37, 163, 90, 15, 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