Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6d22a0fc646e81e9217629541743c400d8ff7c77a504df2bede181c9778f4e6

Tx prefix hash: e5a308745ceb45c76f780e7804d710cc11d6018fde7e70c330dc44d64ad0b47e
Tx public key: 5fa20a0f09b45713924e19365e7a2e84fff65f0938bf40cb01571ead9fc21926
Timestamp: 1718841523 Timestamp [UCT]: 2024-06-19 23:58:43 Age [y:d:h:m:s]: 00:359:00:20:26
Block: 1047954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256514 RingCT/type: yes/0
Extra: 015fa20a0f09b45713924e19365e7a2e84fff65f0938bf40cb01571ead9fc2192602110000000f0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7154801311aa92d20d3d3652c834a20fa726ef2d585e002a62d9ce3e4eea9646 0.600000000000 1517913 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": 1047964, "vin": [ { "gen": { "height": 1047954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7154801311aa92d20d3d3652c834a20fa726ef2d585e002a62d9ce3e4eea9646" } } ], "extra": [ 1, 95, 162, 10, 15, 9, 180, 87, 19, 146, 78, 25, 54, 94, 122, 46, 132, 255, 246, 95, 9, 56, 191, 64, 203, 1, 87, 30, 173, 159, 194, 25, 38, 2, 17, 0, 0, 0, 15, 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