Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9699e346516f4c40bdcd573b3e3979c0848eb210ff4c110c7c720e0ffd88338

Tx prefix hash: c6ed014760af4eb909458e88c952f06df521c2a861347c3fa8072e41124584fc
Tx public key: d1c30629b4ff20f3f694c7e1a7893af7496e8825de9937c2f2633385db9f6a28
Timestamp: 1721597098 Timestamp [UCT]: 2024-07-21 21:24:58 Age [y:d:h:m:s]: 01:153:14:47:48
Block: 1070783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368355 RingCT/type: yes/0
Extra: 01d1c30629b4ff20f3f694c7e1a7893af7496e8825de9937c2f2633385db9f6a2802110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d88df28b8a3a69c367bf666d74dfab8d009f77bb1a14f4b23431735787d8106 0.600000000000 1542760 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": 1070793, "vin": [ { "gen": { "height": 1070783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d88df28b8a3a69c367bf666d74dfab8d009f77bb1a14f4b23431735787d8106" } } ], "extra": [ 1, 209, 195, 6, 41, 180, 255, 32, 243, 246, 148, 199, 225, 167, 137, 58, 247, 73, 110, 136, 37, 222, 153, 55, 194, 242, 99, 51, 133, 219, 159, 106, 40, 2, 17, 0, 0, 0, 8, 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