Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17ca51ef7112d34937dd9cad1b0ed05d56306d9f1d62173713f0d73f897eed6a

Tx prefix hash: 2e2abc80683d6cc161dacf0e692711e56b3958baba92cd562400185191bc9719
Tx public key: 6a853076fd4b36ec3b3c1d8abe8a551e73acfd1497df1b0c8906234bf73f4a4d
Timestamp: 1735820059 Timestamp [UCT]: 2025-01-02 12:14:19 Age [y:d:h:m:s]: 00:132:07:24:07
Block: 1188578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94382 RingCT/type: yes/0
Extra: 016a853076fd4b36ec3b3c1d8abe8a551e73acfd1497df1b0c8906234bf73f4a4d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9dcf8dfc3f360d43083ae03c41149546c8db98df6b9904f102566205c200ba8 0.600000000000 1675081 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": 1188588, "vin": [ { "gen": { "height": 1188578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9dcf8dfc3f360d43083ae03c41149546c8db98df6b9904f102566205c200ba8" } } ], "extra": [ 1, 106, 133, 48, 118, 253, 75, 54, 236, 59, 60, 29, 138, 190, 138, 85, 30, 115, 172, 253, 20, 151, 223, 27, 12, 137, 6, 35, 75, 247, 63, 74, 77, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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