Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f500c9e7f53941607bdb8f41c0ce3500c0496ca28c19f09038f456fec9595871

Tx prefix hash: 48745b46a94c45f9db8a4983b64fc219d7baee314c9c50dc2f28fe11c2a545cd
Tx public key: 534c9241a8c937cb5c70c34f48cc8d43cda765277ed125fd5b67e978619f4e81
Timestamp: 1757908259 Timestamp [UCT]: 2025-09-15 03:50:59 Age [y:d:h:m:s]: 00:099:20:26:22
Block: 1368723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71492 RingCT/type: yes/0
Extra: 01534c9241a8c937cb5c70c34f48cc8d43cda765277ed125fd5b67e978619f4e81021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55613fa7a7e44482fa0be127f61d74222d41a9c4c7917b280444f4e2ac6c42ff 0.600000000000 1856774 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": 1368733, "vin": [ { "gen": { "height": 1368723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55613fa7a7e44482fa0be127f61d74222d41a9c4c7917b280444f4e2ac6c42ff" } } ], "extra": [ 1, 83, 76, 146, 65, 168, 201, 55, 203, 92, 112, 195, 79, 72, 204, 141, 67, 205, 167, 101, 39, 126, 209, 37, 253, 91, 103, 233, 120, 97, 159, 78, 129, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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