Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2392f8c7217b7c9bfeaf1dcfaa63eda1d7fd5ac93180d8acab2280c0d6504b7

Tx prefix hash: 2b66fb6b7e9002589c8cedf9f232947085b673fd33b968a18b8ee4264a6e3a9b
Tx public key: 878709f2f0ab7747770f2302101e79397338e555280c8f7df8e87c9cac2aca9f
Timestamp: 1613705742 Timestamp [UCT]: 2021-02-19 03:35:42 Age [y:d:h:m:s]: 03:355:21:09:58
Block: 201888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1013274 RingCT/type: yes/0
Extra: 01878709f2f0ab7747770f2302101e79397338e555280c8f7df8e87c9cac2aca9f0211000000f957f0ba47000000000000000000

1 output(s) for total of 131.543500970000 dcy

stealth address amount amount idx
00: e43629661d4a1d03aa351f9856bb069751890844f8bd0cd539feab3143e3c378 131.543500970000 413070 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": 201898, "vin": [ { "gen": { "height": 201888 } } ], "vout": [ { "amount": 131543500970, "target": { "key": "e43629661d4a1d03aa351f9856bb069751890844f8bd0cd539feab3143e3c378" } } ], "extra": [ 1, 135, 135, 9, 242, 240, 171, 119, 71, 119, 15, 35, 2, 16, 30, 121, 57, 115, 56, 229, 85, 40, 12, 143, 125, 248, 232, 124, 156, 172, 42, 202, 159, 2, 17, 0, 0, 0, 249, 87, 240, 186, 71, 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