Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9d5dcc14b87635afd8ca9e635cbdb2689358a1a236128a1295cb1a1a6d4e905

Tx prefix hash: 6acd502a40584fd99060d0868f7e2ce8a9cce6fede1d3264656d879a9fffa9ea
Tx public key: 9706a111eccb0f1f2a06195e00c3cc4ba20280ae3f4c9fcad8f761d88ee1340c
Timestamp: 1711781257 Timestamp [UCT]: 2024-03-30 06:47:37 Age [y:d:h:m:s]: 01:046:12:36:30
Block: 989440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294219 RingCT/type: yes/0
Extra: 019706a111eccb0f1f2a06195e00c3cc4ba20280ae3f4c9fcad8f761d88ee1340c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f51b44f4ca07d3d8f2ccd9d329f9954a1496ac249063b2af9b9098fff6f2ecb9 0.600000000000 1449737 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": 989450, "vin": [ { "gen": { "height": 989440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f51b44f4ca07d3d8f2ccd9d329f9954a1496ac249063b2af9b9098fff6f2ecb9" } } ], "extra": [ 1, 151, 6, 161, 17, 236, 203, 15, 31, 42, 6, 25, 94, 0, 195, 204, 75, 162, 2, 128, 174, 63, 76, 159, 202, 216, 247, 97, 216, 142, 225, 52, 12, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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