Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 684a058449dd6d131880d510cf46fb5735630615115b5a715e7e0b6b4b79a25b

Tx prefix hash: 559e1a5b370ec3b0995c93120b048e262de54bab9b183955f6828df822b29a3b
Tx public key: a286fb8ee03158487e6eec53c1ca071405b764e3efd797f69dff26a7c735c652
Timestamp: 1649096747 Timestamp [UCT]: 2022-04-04 18:25:47 Age [y:d:h:m:s]: 02:240:06:03:47
Block: 473167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 691464 RingCT/type: yes/0
Extra: 01a286fb8ee03158487e6eec53c1ca071405b764e3efd797f69dff26a7c735c652021100000013cb8520c2000000000000000000

1 output(s) for total of 16.603572882000 dcy

stealth address amount amount idx
00: 48942b56c70600ad402ed022b0d34f352389efb667611519c15ff8090ec221ce 16.603572882000 892928 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": 473177, "vin": [ { "gen": { "height": 473167 } } ], "vout": [ { "amount": 16603572882, "target": { "key": "48942b56c70600ad402ed022b0d34f352389efb667611519c15ff8090ec221ce" } } ], "extra": [ 1, 162, 134, 251, 142, 224, 49, 88, 72, 126, 110, 236, 83, 193, 202, 7, 20, 5, 183, 100, 227, 239, 215, 151, 246, 157, 255, 38, 167, 199, 53, 198, 82, 2, 17, 0, 0, 0, 19, 203, 133, 32, 194, 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