Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1aa3c558c11aab23a3db16a4e48c0607e8afd4b3db74da89c6fd7ce70849afe0

Tx prefix hash: 73a7c3b2d4ec20e1a8343e80af5f01ea131007ef187f403f551c4099687be3aa
Tx public key: a6923733996585299fa0adcc90a89d327428635f5a02bed0bdef1c18c6e4c1c8
Timestamp: 1761768955 Timestamp [UCT]: 2025-10-29 20:15:55 Age [y:d:h:m:s]: 00:065:03:42:41
Block: 1400730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46646 RingCT/type: yes/0
Extra: 01a6923733996585299fa0adcc90a89d327428635f5a02bed0bdef1c18c6e4c1c8021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd4f8f7a1d0cad42579d25be29467bc3757a0b7ce3fc5bf34cb66102b2c86950 0.600000000000 1889047 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": 1400740, "vin": [ { "gen": { "height": 1400730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd4f8f7a1d0cad42579d25be29467bc3757a0b7ce3fc5bf34cb66102b2c86950" } } ], "extra": [ 1, 166, 146, 55, 51, 153, 101, 133, 41, 159, 160, 173, 204, 144, 168, 157, 50, 116, 40, 99, 95, 90, 2, 190, 208, 189, 239, 28, 24, 198, 228, 193, 200, 2, 17, 0, 0, 0, 4, 223, 90, 36, 122, 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