Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65e4dbd01e2749d1747709630b7b6dcaacd3cec03743caa59767c0904499886b

Tx prefix hash: ae3999ccaf77b046c06a832e86580a0e245e773dd0fe9e54a790377549398dba
Tx public key: 291d2f106e9e92cc32d8880493e982b87570ca85d84a900e62f4baee4f1ba1dc
Timestamp: 1717292455 Timestamp [UCT]: 2024-06-02 01:40:55 Age [y:d:h:m:s]: 00:304:22:04:00
Block: 1035116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217901 RingCT/type: yes/0
Extra: 01291d2f106e9e92cc32d8880493e982b87570ca85d84a900e62f4baee4f1ba1dc02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08e2ea15626ac0f82199ade4a09a2e0c086efad596a3dd6fd1136d21f4719ed9 0.600000000000 1503635 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": 1035126, "vin": [ { "gen": { "height": 1035116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08e2ea15626ac0f82199ade4a09a2e0c086efad596a3dd6fd1136d21f4719ed9" } } ], "extra": [ 1, 41, 29, 47, 16, 110, 158, 146, 204, 50, 216, 136, 4, 147, 233, 130, 184, 117, 112, 202, 133, 216, 74, 144, 14, 98, 244, 186, 238, 79, 27, 161, 220, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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