Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41d2ea6130788cd52abd31e34291bfc81397c9a78da2815d193f006ce3b442c0

Tx prefix hash: b31b93051388406f2995c382400a00a36f7fa29730c55951b94117e214a62063
Tx public key: a2030b340f79808230b56ea04a9d86e782fd10b6ab7c84f8daabea7f771e0751
Timestamp: 1580733741 Timestamp [UCT]: 2020-02-03 12:42:21 Age [y:d:h:m:s]: 04:337:14:22:56
Block: 57886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1132571 RingCT/type: yes/0
Extra: 01a2030b340f79808230b56ea04a9d86e782fd10b6ab7c84f8daabea7f771e0751021100000001e88dac00000000000000000000

1 output(s) for total of 394.709128753000 dcy

stealth address amount amount idx
00: b83bb5fa256b4933e0170b9ea80a7c4717dcf3b9d0e042f43925529af8987a62 394.709128753000 107051 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": 57896, "vin": [ { "gen": { "height": 57886 } } ], "vout": [ { "amount": 394709128753, "target": { "key": "b83bb5fa256b4933e0170b9ea80a7c4717dcf3b9d0e042f43925529af8987a62" } } ], "extra": [ 1, 162, 3, 11, 52, 15, 121, 128, 130, 48, 181, 110, 160, 74, 157, 134, 231, 130, 253, 16, 182, 171, 124, 132, 248, 218, 171, 234, 127, 119, 30, 7, 81, 2, 17, 0, 0, 0, 1, 232, 141, 172, 0, 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