Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66b7d57ff7fdece79d8314afcb0788051ebd334b9ea258e1b72a92e15a62ff46

Tx prefix hash: 8604787768a0269186720fa686c09939d2eee94196be808d86c5b940796fe948
Tx public key: c68869ea31f4b01f3e5d1ce99a2cded6c933cf96e6a5bdc66279f93670e6145a
Timestamp: 1759570140 Timestamp [UCT]: 2025-10-04 09:29:00 Age [y:d:h:m:s]: 00:003:15:24:56
Block: 1382488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2607 RingCT/type: yes/0
Extra: 01c68869ea31f4b01f3e5d1ce99a2cded6c933cf96e6a5bdc66279f93670e6145a021100000006a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79486e1bde10e037787833a10b0c3e940096363e8546d1e576b7e504c011f16a 0.600000000000 1870623 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": 1382498, "vin": [ { "gen": { "height": 1382488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79486e1bde10e037787833a10b0c3e940096363e8546d1e576b7e504c011f16a" } } ], "extra": [ 1, 198, 136, 105, 234, 49, 244, 176, 31, 62, 93, 28, 233, 154, 44, 222, 214, 201, 51, 207, 150, 230, 165, 189, 198, 98, 121, 249, 54, 112, 230, 20, 90, 2, 17, 0, 0, 0, 6, 165, 220, 205, 121, 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