Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73f96fd8eab7e23984c0cd475279055b718c89576bc28ee71670b71776a4b26a

Tx prefix hash: b6b0f2e41d61072629720d24b6bb975de2e6e396c027d8cdff755a63ca3097d1
Tx public key: 866f7d3f37c85573ceaa626bc1e517f368a41d8a56e5f0084556394de0398b34
Timestamp: 1717655706 Timestamp [UCT]: 2024-06-06 06:35:06 Age [y:d:h:m:s]: 00:284:05:54:22
Block: 1038124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203145 RingCT/type: yes/0
Extra: 01866f7d3f37c85573ceaa626bc1e517f368a41d8a56e5f0084556394de0398b340211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47027efe6b9eb66c4aed9df6122537efc05f789b5ea69e747fbca82f71a34546 0.600000000000 1506685 of 15

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": 1038134, "vin": [ { "gen": { "height": 1038124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47027efe6b9eb66c4aed9df6122537efc05f789b5ea69e747fbca82f71a34546" } } ], "extra": [ 1, 134, 111, 125, 63, 55, 200, 85, 115, 206, 170, 98, 107, 193, 229, 23, 243, 104, 164, 29, 138, 86, 229, 240, 8, 69, 86, 57, 77, 224, 57, 139, 52, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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