Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9930c0a735d704dad4c90b5c39b7980330f0f310e74736e17a1dc1c3e0e5c8e

Tx prefix hash: d233002dabee2a7457dc9b061a8eff353c1ae7527cefe59a55e3562320b98712
Tx public key: 958a7997cdb6dee17fc18070f19f663e8b991ea47b79ca7ee5a92eb5092dc76a
Timestamp: 1763295337 Timestamp [UCT]: 2025-11-16 12:15:37 Age [y:d:h:m:s]: 00:075:14:53:38
Block: 1413369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53963 RingCT/type: yes/0
Extra: 01958a7997cdb6dee17fc18070f19f663e8b991ea47b79ca7ee5a92eb5092dc76a02110000000217b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3049494e486ac9fb895b517c1adc4b2497a0a755b728dee39e358485d2b2f847 0.600000000000 1901848 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": 1413379, "vin": [ { "gen": { "height": 1413369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3049494e486ac9fb895b517c1adc4b2497a0a755b728dee39e358485d2b2f847" } } ], "extra": [ 1, 149, 138, 121, 151, 205, 182, 222, 225, 127, 193, 128, 112, 241, 159, 102, 62, 139, 153, 30, 164, 123, 121, 202, 126, 229, 169, 46, 181, 9, 45, 199, 106, 2, 17, 0, 0, 0, 2, 23, 177, 145, 50, 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