Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4023cd6222c5e1f2283e98cf99d48f751e14b2eab9bcfac85ee25945c73b44c4

Tx prefix hash: 9714ecddcc712076ab8e24da3f350d0b9c9c0e6fbd9ff84f8fdfeccaf9474539
Tx public key: 3d61042a8392e793ec3830ef34773a0986acf30173566ed2b3329dd6edc73a2a
Timestamp: 1602086192 Timestamp [UCT]: 2020-10-07 15:56:32 Age [y:d:h:m:s]: 05:029:05:44:31
Block: 140159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1264889 RingCT/type: yes/0
Extra: 013d61042a8392e793ec3830ef34773a0986acf30173566ed2b3329dd6edc73a2a0211000000083a3a2186000000000000000000

1 output(s) for total of 210.666633583000 dcy

stealth address amount amount idx
00: 532c1b0d41dc9e023a0859fbad1c0c5a5b7cce104a351b97ac58984803cdb0a1 210.666633583000 232798 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": 140169, "vin": [ { "gen": { "height": 140159 } } ], "vout": [ { "amount": 210666633583, "target": { "key": "532c1b0d41dc9e023a0859fbad1c0c5a5b7cce104a351b97ac58984803cdb0a1" } } ], "extra": [ 1, 61, 97, 4, 42, 131, 146, 231, 147, 236, 56, 48, 239, 52, 119, 58, 9, 134, 172, 243, 1, 115, 86, 110, 210, 179, 50, 157, 214, 237, 199, 58, 42, 2, 17, 0, 0, 0, 8, 58, 58, 33, 134, 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