Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e73033e996f13fa2dc6d3a0804805e35e42870f8e74c2a669883c90bf0e42e87

Tx prefix hash: 8f5adc52322975f42bc31788429d44c7dffe269e2558bcf05262888fb2e37fcb
Tx public key: 45fe3b28da7a461fb12fbe9463e01c53fc0a2bdcc43886dfedff1e36b50804dc
Timestamp: 1581513247 Timestamp [UCT]: 2020-02-12 13:14:07 Age [y:d:h:m:s]: 04:267:15:49:47
Block: 63381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1083478 RingCT/type: yes/0
Extra: 0145fe3b28da7a461fb12fbe9463e01c53fc0a2bdcc43886dfedff1e36b50804dc021100000001724f989b000000000000000000

1 output(s) for total of 378.436702553000 dcy

stealth address amount amount idx
00: 64db4e81785ab30c9c9c6571fea156d4912a2c4fa6e39727935c36db12dbc037 378.436702553000 116897 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": 63391, "vin": [ { "gen": { "height": 63381 } } ], "vout": [ { "amount": 378436702553, "target": { "key": "64db4e81785ab30c9c9c6571fea156d4912a2c4fa6e39727935c36db12dbc037" } } ], "extra": [ 1, 69, 254, 59, 40, 218, 122, 70, 31, 177, 47, 190, 148, 99, 224, 28, 83, 252, 10, 43, 220, 196, 56, 134, 223, 237, 255, 30, 54, 181, 8, 4, 220, 2, 17, 0, 0, 0, 1, 114, 79, 152, 155, 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