Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67252971f2ee8b52a9397d9ad161b46efedc0af91a94da6aee1c15d5a812cbfe

Tx prefix hash: e5580156b4161f4dbc42cdfb8e915edb8804c2bf1755198b34d6b491d30a2bd2
Tx public key: d4ea5de81727c246f783647a9a656e1c69c662ec82afc84ba6e0968ac6eb263f
Timestamp: 1736295639 Timestamp [UCT]: 2025-01-08 00:20:39 Age [y:d:h:m:s]: 00:108:09:12:30
Block: 1192512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77265 RingCT/type: yes/0
Extra: 01d4ea5de81727c246f783647a9a656e1c69c662ec82afc84ba6e0968ac6eb263f0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5089bf6e5333f73f7e58d974eab85c07900dfbb08bc9719ffab086712588e3e0 0.600000000000 1679065 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": 1192522, "vin": [ { "gen": { "height": 1192512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5089bf6e5333f73f7e58d974eab85c07900dfbb08bc9719ffab086712588e3e0" } } ], "extra": [ 1, 212, 234, 93, 232, 23, 39, 194, 70, 247, 131, 100, 122, 154, 101, 110, 28, 105, 198, 98, 236, 130, 175, 200, 75, 166, 224, 150, 138, 198, 235, 38, 63, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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