Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec957c037360fd8cdb169f98f53a4000937333144aa8bc289c13e786330a5a05

Tx prefix hash: 5f758a259d0be31cef080a07cdff91cae39d146c21a9e3cba10002a968243755
Tx public key: cddb5b9efea6e0b7dd4d02b3b6ba0bc8ec01eede15fd09f8ced15d17ebf5da99
Timestamp: 1727588416 Timestamp [UCT]: 2024-09-29 05:40:16 Age [y:d:h:m:s]: 01:045:10:54:39
Block: 1120467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290883 RingCT/type: yes/0
Extra: 01cddb5b9efea6e0b7dd4d02b3b6ba0bc8ec01eede15fd09f8ced15d17ebf5da99021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44e26116c5fc79bdf86c3dbd01edd766b3bbef47af753adfcb1f2e901f386d0f 0.600000000000 1602394 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": 1120477, "vin": [ { "gen": { "height": 1120467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44e26116c5fc79bdf86c3dbd01edd766b3bbef47af753adfcb1f2e901f386d0f" } } ], "extra": [ 1, 205, 219, 91, 158, 254, 166, 224, 183, 221, 77, 2, 179, 182, 186, 11, 200, 236, 1, 238, 222, 21, 253, 9, 248, 206, 209, 93, 23, 235, 245, 218, 153, 2, 17, 0, 0, 0, 2, 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