Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0b78a35461ece66005256bd28e20ed8a89587f269bf1ce36151b35268e601d9

Tx prefix hash: 801123bb9d228ad4841f694f51ae55afb841edd828cc52372d9d9b1f97fd4e7f
Tx public key: fea60384feb5ff2d2719d5a1cf153b943335abfce256c8146efd89bccf95ef4a
Timestamp: 1580888308 Timestamp [UCT]: 2020-02-05 07:38:28 Age [y:d:h:m:s]: 04:289:18:36:29
Block: 59013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1098509 RingCT/type: yes/0
Extra: 01fea60384feb5ff2d2719d5a1cf153b943335abfce256c8146efd89bccf95ef4a021100000001bd0f9f9f000000000000000000

1 output(s) for total of 391.290813182000 dcy

stealth address amount amount idx
00: 37037ed3c8646828a50f15d64b2fbfd73a2a19bb6e2946441e73fa81b5fa6dcd 391.290813182000 108993 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": 59023, "vin": [ { "gen": { "height": 59013 } } ], "vout": [ { "amount": 391290813182, "target": { "key": "37037ed3c8646828a50f15d64b2fbfd73a2a19bb6e2946441e73fa81b5fa6dcd" } } ], "extra": [ 1, 254, 166, 3, 132, 254, 181, 255, 45, 39, 25, 213, 161, 207, 21, 59, 148, 51, 53, 171, 252, 226, 86, 200, 20, 110, 253, 137, 188, 207, 149, 239, 74, 2, 17, 0, 0, 0, 1, 189, 15, 159, 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