Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd4fe58257c3c63c7744ab78340c26dd69c010b110a4c7cb5ec75511b2ed203a

Tx prefix hash: 94bfa4db6554e978fa2ce5239f0bd7d4f1841185f5f1c5586e94f5bceeebba3c
Tx public key: 0471c783c71ab5bad860cbfdade1157534eb7836a0444e45d08723b5e58e5d27
Timestamp: 1720429150 Timestamp [UCT]: 2024-07-08 08:59:10 Age [y:d:h:m:s]: 00:275:19:22:29
Block: 1061122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197054 RingCT/type: yes/0
Extra: 010471c783c71ab5bad860cbfdade1157534eb7836a0444e45d08723b5e58e5d27021100000008c26d3a99000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 921a42c82a5a533d50792d852a906cccbb5df8d8fd1bc4ba5575b1a5aa830302 0.600000000000 1531613 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": 1061132, "vin": [ { "gen": { "height": 1061122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "921a42c82a5a533d50792d852a906cccbb5df8d8fd1bc4ba5575b1a5aa830302" } } ], "extra": [ 1, 4, 113, 199, 131, 199, 26, 181, 186, 216, 96, 203, 253, 173, 225, 21, 117, 52, 235, 120, 54, 160, 68, 78, 69, 208, 135, 35, 181, 229, 142, 93, 39, 2, 17, 0, 0, 0, 8, 194, 109, 58, 153, 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