Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04b5de5343d390d6d5ef37a8255fcae55e8759338b063e894531a00617af34a4

Tx prefix hash: d9d1207ead188d9cb26e9315683fbf8c8fec07a53c9a24adf21807c7e56baed7
Tx public key: cf5c72c04618a8d394afffe1fe520330afe30f7e52af2a4659811349f6dd820b
Timestamp: 1580768798 Timestamp [UCT]: 2020-02-03 22:26:38 Age [y:d:h:m:s]: 04:277:00:55:36
Block: 57940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1089456 RingCT/type: yes/0
Extra: 01cf5c72c04618a8d394afffe1fe520330afe30f7e52af2a4659811349f6dd820b0211000000038a2ee0d9000000000000000000

1 output(s) for total of 394.476875186000 dcy

stealth address amount amount idx
00: 058bbdcd60088b00c091cec5ed4435a94570c05f4ec79ece5035c4ae6f9e97a7 394.476875186000 107151 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": 57950, "vin": [ { "gen": { "height": 57940 } } ], "vout": [ { "amount": 394476875186, "target": { "key": "058bbdcd60088b00c091cec5ed4435a94570c05f4ec79ece5035c4ae6f9e97a7" } } ], "extra": [ 1, 207, 92, 114, 192, 70, 24, 168, 211, 148, 175, 255, 225, 254, 82, 3, 48, 175, 227, 15, 126, 82, 175, 42, 70, 89, 129, 19, 73, 246, 221, 130, 11, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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