Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d47ea49e1652661ec4cb43e5e1f4fe26b6b71833eb9267412bf29b94b3f1cac8

Tx prefix hash: e036cde647864517a309cd8309bd66c460932c9abf1ffe67ed2f3c1a04feb97f
Tx public key: 8a547910fe1e01e91268e1bc8a1d532811c960c8a663c48da10c13a96929f0e1
Timestamp: 1635574658 Timestamp [UCT]: 2021-10-30 06:17:38 Age [y:d:h:m:s]: 03:198:09:11:03
Block: 363454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 920093 RingCT/type: yes/0
Extra: 018a547910fe1e01e91268e1bc8a1d532811c960c8a663c48da10c13a96929f0e1021100000006a272b9cb000000000000000000

1 output(s) for total of 38.346561296000 dcy

stealth address amount amount idx
00: c2dff3bbd8d7b3b03d3610306439563fe9ba57cae76db2ccb2a945bc301d4609 38.346561296000 738694 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": 363464, "vin": [ { "gen": { "height": 363454 } } ], "vout": [ { "amount": 38346561296, "target": { "key": "c2dff3bbd8d7b3b03d3610306439563fe9ba57cae76db2ccb2a945bc301d4609" } } ], "extra": [ 1, 138, 84, 121, 16, 254, 30, 1, 233, 18, 104, 225, 188, 138, 29, 83, 40, 17, 201, 96, 200, 166, 99, 196, 141, 161, 12, 19, 169, 105, 41, 240, 225, 2, 17, 0, 0, 0, 6, 162, 114, 185, 203, 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