Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8adf61abf7f8648d50f9d5164798ab18cd000424b981bbf223302df61c3a8d4f

Tx prefix hash: bb6e11fb9f96436575d860cfe6aca7a6aafacfa4e135f494d1c460041d07875d
Tx public key: f011582b081f53bbc7ce06956c7f74c7c2042e0e4001cb405d2922b8310d8de2
Timestamp: 1582937123 Timestamp [UCT]: 2020-02-29 00:45:23 Age [y:d:h:m:s]: 04:338:01:32:19
Block: 73708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1135057 RingCT/type: yes/0
Extra: 01f011582b081f53bbc7ce06956c7f74c7c2042e0e4001cb405d2922b8310d8de20211000000128a2ee0d9000000000000000000

1 output(s) for total of 349.772215035000 dcy

stealth address amount amount idx
00: cf6c92bd52fb0a9560c9e7cfbaeb745081308a1648d6bf9efc0925a8959c217a 349.772215035000 136037 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": 73718, "vin": [ { "gen": { "height": 73708 } } ], "vout": [ { "amount": 349772215035, "target": { "key": "cf6c92bd52fb0a9560c9e7cfbaeb745081308a1648d6bf9efc0925a8959c217a" } } ], "extra": [ 1, 240, 17, 88, 43, 8, 31, 83, 187, 199, 206, 6, 149, 108, 127, 116, 199, 194, 4, 46, 14, 64, 1, 203, 64, 93, 41, 34, 184, 49, 13, 141, 226, 2, 17, 0, 0, 0, 18, 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