Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a64eccccdc2ef22ea68ef58b0053c34956b054bb24b4ecec23f399653035906

Tx prefix hash: bb6ef568a552d72b1773c1982bbf83f53b59f21556eaf78ac9a66fc23405ecd1
Tx public key: 4e976b8feeb1b4232715aeb5f89e1e0cd93b08bdf2f3847aaba6c1132f5c0256
Timestamp: 1722122067 Timestamp [UCT]: 2024-07-27 23:14:27 Age [y:d:h:m:s]: 00:264:15:25:47
Block: 1075150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189058 RingCT/type: yes/0
Extra: 014e976b8feeb1b4232715aeb5f89e1e0cd93b08bdf2f3847aaba6c1132f5c025602110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8665c8567b0cb27bf176ef4c5ed66ea90f3954bc4dcb39a3ff94a7cf4a8f1560 0.600000000000 1547673 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": 1075160, "vin": [ { "gen": { "height": 1075150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8665c8567b0cb27bf176ef4c5ed66ea90f3954bc4dcb39a3ff94a7cf4a8f1560" } } ], "extra": [ 1, 78, 151, 107, 143, 238, 177, 180, 35, 39, 21, 174, 181, 248, 158, 30, 12, 217, 59, 8, 189, 242, 243, 132, 122, 171, 166, 193, 19, 47, 92, 2, 86, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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