Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3d567aab76f7fbad156ef6511e180f4e0ad4f7e78b9bc2161b872ebb1e8d25e

Tx prefix hash: 29f4b09ad09c1a00c9c7993b36aa5592790c444956b8e419e288104e6c18414f
Tx public key: b3d0242265acc42243e39a7c08361a328ca6630fd4885fb4f166efe04074d545
Timestamp: 1762423758 Timestamp [UCT]: 2025-11-06 10:09:18 Age [y:d:h:m:s]: 00:060:11:48:29
Block: 1406127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43351 RingCT/type: yes/0
Extra: 01b3d0242265acc42243e39a7c08361a328ca6630fd4885fb4f166efe04074d5450211000000045dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d843e2468fe190f800f1dbc968699cee97d2db4b600ba21738d6a9d77285adb6 0.600000000000 1894510 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": 1406137, "vin": [ { "gen": { "height": 1406127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d843e2468fe190f800f1dbc968699cee97d2db4b600ba21738d6a9d77285adb6" } } ], "extra": [ 1, 179, 208, 36, 34, 101, 172, 196, 34, 67, 227, 154, 124, 8, 54, 26, 50, 140, 166, 99, 15, 212, 136, 95, 180, 241, 102, 239, 224, 64, 116, 213, 69, 2, 17, 0, 0, 0, 4, 93, 251, 190, 42, 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