Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0a9d0986b6d96f727fe936d40f3958b2e3760d22bd3265a4e8410569311c74c

Tx prefix hash: d53d5edaed9f0b88a5ceb8f774371d42eeb4f1a65fd2818ca75ebd6b3b038745
Tx public key: 1382c9e95a7f0c158f7500ccdd3ade14ebf8044711a58c1648412a2ec4b28fb4
Timestamp: 1578842462 Timestamp [UCT]: 2020-01-12 15:21:02 Age [y:d:h:m:s]: 05:293:16:51:54
Block: 44059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1357744 RingCT/type: yes/0
Extra: 011382c9e95a7f0c158f7500ccdd3ade14ebf8044711a58c1648412a2ec4b28fb40211000000144943cd9f000000000000000000

1 output(s) for total of 438.555440107000 dcy

stealth address amount amount idx
00: 15cc488904d0047d004d9d6c4833a9066810446838d497af2980deaf7971eca8 438.555440107000 80053 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": 44069, "vin": [ { "gen": { "height": 44059 } } ], "vout": [ { "amount": 438555440107, "target": { "key": "15cc488904d0047d004d9d6c4833a9066810446838d497af2980deaf7971eca8" } } ], "extra": [ 1, 19, 130, 201, 233, 90, 127, 12, 21, 143, 117, 0, 204, 221, 58, 222, 20, 235, 248, 4, 71, 17, 165, 140, 22, 72, 65, 42, 46, 196, 178, 143, 180, 2, 17, 0, 0, 0, 20, 73, 67, 205, 159, 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