Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a13d8254787c5e004106f9a4ad2d165f5fff3d394bb259499b6b6e20427c9bf

Tx prefix hash: ccd9f6fa8afe7b8e466ba9b2cdbb4ff6172e40b475ea5f647f359d1688904c7c
Tx public key: b7be16e46488466ea34a890992d25f7d6e30dc65343e256761754e48ec998bcd
Timestamp: 1711511297 Timestamp [UCT]: 2024-03-27 03:48:17 Age [y:d:h:m:s]: 01:221:05:44:19
Block: 987203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416773 RingCT/type: yes/0
Extra: 01b7be16e46488466ea34a890992d25f7d6e30dc65343e256761754e48ec998bcd0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4da2248951cd6e06f319aa86d683bd713a4046805e29686b550f067e0ae5afb4 0.600000000000 1447444 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": 987213, "vin": [ { "gen": { "height": 987203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4da2248951cd6e06f319aa86d683bd713a4046805e29686b550f067e0ae5afb4" } } ], "extra": [ 1, 183, 190, 22, 228, 100, 136, 70, 110, 163, 74, 137, 9, 146, 210, 95, 125, 110, 48, 220, 101, 52, 62, 37, 103, 97, 117, 78, 72, 236, 153, 139, 205, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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