Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be2485dc749899bdad0673be427e8ed0b0b63a5ec2d65943509a7ad83d5476f9

Tx prefix hash: 78b478e47a470b0b54c577940deedf0b36747dfa4d3c96da2169d42e72ffd796
Tx public key: 63834720f769c917ae29894df9b6e71d9d5a72c54610567208e7e61763e1f881
Timestamp: 1703508703 Timestamp [UCT]: 2023-12-25 12:51:43 Age [y:d:h:m:s]: 01:319:21:39:59
Block: 920836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487469 RingCT/type: yes/0
Extra: 0163834720f769c917ae29894df9b6e71d9d5a72c54610567208e7e61763e1f88102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64cb69988c2a5463e330c6633838615997ac7b7ef3df3d40ce3d26ed5e1b7c7e 0.600000000000 1378520 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": 920846, "vin": [ { "gen": { "height": 920836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64cb69988c2a5463e330c6633838615997ac7b7ef3df3d40ce3d26ed5e1b7c7e" } } ], "extra": [ 1, 99, 131, 71, 32, 247, 105, 201, 23, 174, 41, 137, 77, 249, 182, 231, 29, 157, 90, 114, 197, 70, 16, 86, 114, 8, 231, 230, 23, 99, 225, 248, 129, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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