Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 696354f2b9d65ec5ca566c251e9c0c6b561336c068d4ef42152e80509e617bf6

Tx prefix hash: 511b6664f64ded1f6ce688f230267c66373207957a018df98e29342642b51904
Tx public key: 5de792eee429ba353c53899ff8c7dc812c1a33907be633504cf1f8a01732b0a7
Timestamp: 1577174196 Timestamp [UCT]: 2019-12-24 07:56:36 Age [y:d:h:m:s]: 05:072:01:05:44
Block: 30508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201344 RingCT/type: yes/0
Extra: 015de792eee429ba353c53899ff8c7dc812c1a33907be633504cf1f8a01732b0a70211000000074943cd9f000000000000000000

1 output(s) for total of 486.320621711000 dcy

stealth address amount amount idx
00: caa0e32ae27145f5a61ce9afdb7f0c75b87a8738255a652c15f0b7a3166d578f 486.320621711000 50370 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": 30518, "vin": [ { "gen": { "height": 30508 } } ], "vout": [ { "amount": 486320621711, "target": { "key": "caa0e32ae27145f5a61ce9afdb7f0c75b87a8738255a652c15f0b7a3166d578f" } } ], "extra": [ 1, 93, 231, 146, 238, 228, 41, 186, 53, 60, 83, 137, 159, 248, 199, 220, 129, 44, 26, 51, 144, 123, 230, 51, 80, 76, 241, 248, 160, 23, 50, 176, 167, 2, 17, 0, 0, 0, 7, 73, 67, 205, 159, 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