Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cd3e4409cb696caf9ad0c723d22d15ed44dcd94ffaa27429e659a7a150f86a2

Tx prefix hash: f9fd2031283517a384d828f746adf96c4d041c010aabd02adb25c022a60f0f8e
Tx public key: e5af7e5eaafe18f38df1a0174748b0a9324a7da6af58a2a4bb13ba5ade15f3f5
Timestamp: 1648154937 Timestamp [UCT]: 2022-03-24 20:48:57 Age [y:d:h:m:s]: 03:222:06:44:26
Block: 465650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 936730 RingCT/type: yes/0
Extra: 01e5af7e5eaafe18f38df1a0174748b0a9324a7da6af58a2a4bb13ba5ade15f3f5021100000004a272b9cb000000000000000000

1 output(s) for total of 17.583628733000 dcy

stealth address amount amount idx
00: 7cfe67ca618db2a4cc77b810039cc10894ec39c99af0fce4aeff7b0ff34d89ac 17.583628733000 883801 of 0

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": 465660, "vin": [ { "gen": { "height": 465650 } } ], "vout": [ { "amount": 17583628733, "target": { "key": "7cfe67ca618db2a4cc77b810039cc10894ec39c99af0fce4aeff7b0ff34d89ac" } } ], "extra": [ 1, 229, 175, 126, 94, 170, 254, 24, 243, 141, 241, 160, 23, 71, 72, 176, 169, 50, 74, 125, 166, 175, 88, 162, 164, 187, 19, 186, 90, 222, 21, 243, 245, 2, 17, 0, 0, 0, 4, 162, 114, 185, 203, 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