Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26a54c660bf254c780332bf72e62678b39809a6f1a896faad2ac89329f735f48

Tx prefix hash: 86e474b9b7801c1a19eb4c5d16cf3daab355f8cbb2c1c8fc649a6134384a6ad6
Tx public key: 0eec7ddeb8f95eb71b4ae89ec4bdf69f5f0612a3bb2a7324e16ac949eb7669c8
Timestamp: 1648880117 Timestamp [UCT]: 2022-04-02 06:15:17 Age [y:d:h:m:s]: 03:025:13:12:47
Block: 471450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 798629 RingCT/type: yes/0
Extra: 010eec7ddeb8f95eb71b4ae89ec4bdf69f5f0612a3bb2a7324e16ac949eb7669c802110000000506faf294000000000000000000

1 output(s) for total of 16.822505894000 dcy

stealth address amount amount idx
00: ffd5ba498e28e9fce349ec8e35033b5e442ec1686d1b240e3718c47a0a54fd04 16.822505894000 890794 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": 471460, "vin": [ { "gen": { "height": 471450 } } ], "vout": [ { "amount": 16822505894, "target": { "key": "ffd5ba498e28e9fce349ec8e35033b5e442ec1686d1b240e3718c47a0a54fd04" } } ], "extra": [ 1, 14, 236, 125, 222, 184, 249, 94, 183, 27, 74, 232, 158, 196, 189, 246, 159, 95, 6, 18, 163, 187, 42, 115, 36, 225, 106, 201, 73, 235, 118, 105, 200, 2, 17, 0, 0, 0, 5, 6, 250, 242, 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