Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81c06a6629be45b90aa5aab507d73b718ecbf833ad7ab7ae3cd7abec12fb62d4

Tx prefix hash: 326b61f7a13cbdb379cae59f4e3916aa3b8acc92295902de9860ff43237f50b9
Tx public key: 529b6f2071b107fa868fd3ab451bae61151d6867a9359e5e847294c63cff4f3d
Timestamp: 1762740092 Timestamp [UCT]: 2025-11-10 02:01:32 Age [y:d:h:m:s]: 00:056:19:02:19
Block: 1408767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40681 RingCT/type: yes/0
Extra: 01529b6f2071b107fa868fd3ab451bae61151d6867a9359e5e847294c63cff4f3d021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5af6a95f970a6507579fa748ceb220f40fdcb377603822a06e58debc9dc5830b 0.600000000000 1897198 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": 1408777, "vin": [ { "gen": { "height": 1408767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5af6a95f970a6507579fa748ceb220f40fdcb377603822a06e58debc9dc5830b" } } ], "extra": [ 1, 82, 155, 111, 32, 113, 177, 7, 250, 134, 143, 211, 171, 69, 27, 174, 97, 21, 29, 104, 103, 169, 53, 158, 94, 132, 114, 148, 198, 60, 255, 79, 61, 2, 17, 0, 0, 0, 4, 223, 90, 36, 122, 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