Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24167ea6d033a3fd2e57d8620ecd423f80516201ad5cedffc05644d6e47ce075

Tx prefix hash: 73a93b823c6c79ce611d560766b48fa9e6f459c5d1ef4649289a845227626a8d
Tx public key: 3f57e81755436a130f671720e89959df55d27876bca4017823a368ae5d683c3f
Timestamp: 1724592863 Timestamp [UCT]: 2024-08-25 13:34:23 Age [y:d:h:m:s]: 01:074:07:23:20
Block: 1095625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311561 RingCT/type: yes/0
Extra: 013f57e81755436a130f671720e89959df55d27876bca4017823a368ae5d683c3f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd7f9f942aa69aee957cc5b0f577f3cae5d5d79b4d7711aa4fcc45738d2faeef 0.600000000000 1570806 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": 1095635, "vin": [ { "gen": { "height": 1095625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd7f9f942aa69aee957cc5b0f577f3cae5d5d79b4d7711aa4fcc45738d2faeef" } } ], "extra": [ 1, 63, 87, 232, 23, 85, 67, 106, 19, 15, 103, 23, 32, 232, 153, 89, 223, 85, 210, 120, 118, 188, 164, 1, 120, 35, 163, 104, 174, 93, 104, 60, 63, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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