Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0f1bad416398827d3bd9f664cdb5acb2e9ebcf8dcdde513db7c93c51cb4f28b

Tx prefix hash: bb13ad2ce1de873540cc9e057709f51a6a6f5da844e8ecc667536223b2ea0e69
Tx public key: 79dc2a633839d1327410b96ff0618845d9407e8feffdade252cb3e90aa3f28e9
Timestamp: 1765997589 Timestamp [UCT]: 2025-12-17 18:53:09 Age [y:d:h:m:s]: 00:042:14:55:11
Block: 1435756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30350 RingCT/type: yes/0
Extra: 0179dc2a633839d1327410b96ff0618845d9407e8feffdade252cb3e90aa3f28e90211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f267d5d06557cefeb497773a3985249b937a7ae82077a77dfefd634ad2813d57 0.600000000000 1924557 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": 1435766, "vin": [ { "gen": { "height": 1435756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f267d5d06557cefeb497773a3985249b937a7ae82077a77dfefd634ad2813d57" } } ], "extra": [ 1, 121, 220, 42, 99, 56, 57, 209, 50, 116, 16, 185, 111, 240, 97, 136, 69, 217, 64, 126, 143, 239, 253, 173, 226, 82, 203, 62, 144, 170, 63, 40, 233, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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