Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaf4ac3ca97c77ac6c48c06c759fa48e5d31e33d3178c4573b8c57f5d0e4f7dc

Tx prefix hash: da007c8d21c77380c07818c97bad82e3a71d8508a68af5afca14b101237479e4
Tx public key: e4b878df67f8aeeeba2b861ed306f519221dce1c5cb202b494b3890235b9d923
Timestamp: 1574725376 Timestamp [UCT]: 2019-11-25 23:42:56 Age [y:d:h:m:s]: 05:043:01:21:54
Block: 17516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1173599 RingCT/type: yes/0
Extra: 01e4b878df67f8aeeeba2b861ed306f519221dce1c5cb202b494b3890235b9d92302110000000280094f5e000000000000000000

1 output(s) for total of 536.986170716000 dcy

stealth address amount amount idx
00: 373a18440f744b868f215b5cce30fec54e833e97c0e4f566c6147fc1afb5b2d0 536.986170716000 25570 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": 17526, "vin": [ { "gen": { "height": 17516 } } ], "vout": [ { "amount": 536986170716, "target": { "key": "373a18440f744b868f215b5cce30fec54e833e97c0e4f566c6147fc1afb5b2d0" } } ], "extra": [ 1, 228, 184, 120, 223, 103, 248, 174, 238, 186, 43, 134, 30, 211, 6, 245, 25, 34, 29, 206, 28, 92, 178, 2, 180, 148, 179, 137, 2, 53, 185, 217, 35, 2, 17, 0, 0, 0, 2, 128, 9, 79, 94, 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