Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 319b0deda97e1172590fe19f85c50ed3e263220e1d54790e23a5a567a63b6c6b

Tx prefix hash: 7a3138d16674481a5fd6f90cc7410b6d673c46cf1b5044e1fe60e9e44bf6893a
Tx public key: 507cf75027a68d3d7d4d8e3248efe8c53484ec0e1f04aac9491f83ac770d45ff
Timestamp: 1756111842 Timestamp [UCT]: 2025-08-25 08:50:42 Age [y:d:h:m:s]: 00:087:22:55:19
Block: 1354020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62780 RingCT/type: yes/0
Extra: 01507cf75027a68d3d7d4d8e3248efe8c53484ec0e1f04aac9491f83ac770d45ff021100000008b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c5f169dae73fe23497fcc8c5e2e74aea6e855f65b8f5bbfb91983e3deb38d1b 0.600000000000 1842001 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": 1354030, "vin": [ { "gen": { "height": 1354020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c5f169dae73fe23497fcc8c5e2e74aea6e855f65b8f5bbfb91983e3deb38d1b" } } ], "extra": [ 1, 80, 124, 247, 80, 39, 166, 141, 61, 125, 77, 142, 50, 72, 239, 232, 197, 52, 132, 236, 14, 31, 4, 170, 201, 73, 31, 131, 172, 119, 13, 69, 255, 2, 17, 0, 0, 0, 8, 178, 247, 132, 196, 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