Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4375efa50b4072fe88f7a1a853c7157e4d248621a70f716dd252a4792d6eb6f9

Tx prefix hash: f3dbd561617269443c4e0fcd50c7e089428cc72ccb60a5fd742d9911162121ed
Tx public key: b15e2015895b52133105788a4a873dd341cdc831062f2e35b7aaabf9eccbe526
Timestamp: 1698382029 Timestamp [UCT]: 2023-10-27 04:47:09 Age [y:d:h:m:s]: 01:154:13:10:31
Block: 878552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371445 RingCT/type: yes/0
Extra: 01b15e2015895b52133105788a4a873dd341cdc831062f2e35b7aaabf9eccbe5260211000000034b8f5122000000000000000000

1 output(s) for total of 0.753342614000 dcy

stealth address amount amount idx
00: 4d4f913a882f3cf335ce0d9bf47b06b0efccfdca7a3e111f9a391cf7be224b9d 0.753342614000 1334004 of 0

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": 878562, "vin": [ { "gen": { "height": 878552 } } ], "vout": [ { "amount": 753342614, "target": { "key": "4d4f913a882f3cf335ce0d9bf47b06b0efccfdca7a3e111f9a391cf7be224b9d" } } ], "extra": [ 1, 177, 94, 32, 21, 137, 91, 82, 19, 49, 5, 120, 138, 74, 135, 61, 211, 65, 205, 200, 49, 6, 47, 46, 53, 183, 170, 171, 249, 236, 203, 229, 38, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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