Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 939d765f1c025a6eb4e94990ff8eea4a77b626fe492bf83cb605e15edac195b5

Tx prefix hash: f5c2b7e71971f73c2a6dacfe0ddeb25523eec7ad5432c9bfa3b3aeca1e8193dc
Tx public key: 1057d26f67b15ecb6826d308fafde0ea010d78f1727c0adc05ec577534d20cd6
Timestamp: 1745512182 Timestamp [UCT]: 2025-04-24 16:29:42 Age [y:d:h:m:s]: 00:210:05:50:17
Block: 1268549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147980 RingCT/type: yes/0
Extra: 011057d26f67b15ecb6826d308fafde0ea010d78f1727c0adc05ec577534d20cd60211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2c4c93568fae8770fcda89b29086fccae85d196dc2ca382e2faafb9fcd8493e 0.600000000000 1755778 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": 1268559, "vin": [ { "gen": { "height": 1268549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2c4c93568fae8770fcda89b29086fccae85d196dc2ca382e2faafb9fcd8493e" } } ], "extra": [ 1, 16, 87, 210, 111, 103, 177, 94, 203, 104, 38, 211, 8, 250, 253, 224, 234, 1, 13, 120, 241, 114, 124, 10, 220, 5, 236, 87, 117, 52, 210, 12, 214, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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