Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8a744bd6ec02b5e4cf76e424de891d6a659e3927d90a77a80e564580beb5327

Tx prefix hash: 8cd901e1bfdb22f484a0c1fdc2022bd2ce1a08027ab122b22c257c6fb3f22848
Tx public key: 5197ab84b7916c5cea44099cb893e60054ecb87ae8fbaa46967c35312c401864
Timestamp: 1583629620 Timestamp [UCT]: 2020-03-08 01:07:00 Age [y:d:h:m:s]: 04:255:17:03:13
Block: 78163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1077686 RingCT/type: yes/0
Extra: 015197ab84b7916c5cea44099cb893e60054ecb87ae8fbaa46967c35312c401864021100000001a33b4a85000000000000000000

1 output(s) for total of 338.075988572000 dcy

stealth address amount amount idx
00: 2baf7de971e938edf1b9e88ab70557543d129b631a50b67851f12af3c3bb20f5 338.075988572000 143595 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": 78173, "vin": [ { "gen": { "height": 78163 } } ], "vout": [ { "amount": 338075988572, "target": { "key": "2baf7de971e938edf1b9e88ab70557543d129b631a50b67851f12af3c3bb20f5" } } ], "extra": [ 1, 81, 151, 171, 132, 183, 145, 108, 92, 234, 68, 9, 156, 184, 147, 230, 0, 84, 236, 184, 122, 232, 251, 170, 70, 150, 124, 53, 49, 44, 64, 24, 100, 2, 17, 0, 0, 0, 1, 163, 59, 74, 133, 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