Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9f40437553f41642d23c984f4c194a8bf2ec05487c3ee9ae0545fe3385cfb9b

Tx prefix hash: 6c9d57741b5c32cd2bca336544da96a517866fd29aeb3ed2ea324e4d59aa40e4
Tx public key: 12f7bd0ba947d0e8c214496f99fad9add9e142234399f0c136bf93ce0abb1356
Timestamp: 1719866548 Timestamp [UCT]: 2024-07-01 20:42:28 Age [y:d:h:m:s]: 00:272:21:38:07
Block: 1056444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194995 RingCT/type: yes/0
Extra: 0112f7bd0ba947d0e8c214496f99fad9add9e142234399f0c136bf93ce0abb13560211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8d6380a83b6dd0eeb415d3cc4de6cada79d82ccc40164c5a8853c2a42dbb55e 0.600000000000 1526857 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": 1056454, "vin": [ { "gen": { "height": 1056444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8d6380a83b6dd0eeb415d3cc4de6cada79d82ccc40164c5a8853c2a42dbb55e" } } ], "extra": [ 1, 18, 247, 189, 11, 169, 71, 208, 232, 194, 20, 73, 111, 153, 250, 217, 173, 217, 225, 66, 35, 67, 153, 240, 193, 54, 191, 147, 206, 10, 187, 19, 86, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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