Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddba2dd7533d3713d1c4b7f73e0236a7d68363a0ebb751a9ac756977a823b9ff

Tx prefix hash: fde66f2cffaed456af6817d198cee4d41978777f075c7059174e4d4c52c3911a
Tx public key: 2df2e9c2e436be49d05c736a25a34035af35d92630f1ad36a495a55507a27269
Timestamp: 1753189013 Timestamp [UCT]: 2025-07-22 12:56:53 Age [y:d:h:m:s]: 00:190:17:47:43
Block: 1330960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135045 RingCT/type: yes/0
Extra: 012df2e9c2e436be49d05c736a25a34035af35d92630f1ad36a495a55507a2726902110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8488a77ebd0ef44a098e39e5d8a2d2ec1fe54858b33dc098f13d10536b2a1a7a 0.600000000000 1818753 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": 1330970, "vin": [ { "gen": { "height": 1330960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8488a77ebd0ef44a098e39e5d8a2d2ec1fe54858b33dc098f13d10536b2a1a7a" } } ], "extra": [ 1, 45, 242, 233, 194, 228, 54, 190, 73, 208, 92, 115, 106, 37, 163, 64, 53, 175, 53, 217, 38, 48, 241, 173, 54, 164, 149, 165, 85, 7, 162, 114, 105, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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