Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 556968800626654f9930630db117bbba4a75b06ecaa7bbaf2bd94f2704bfbf49

Tx prefix hash: 47ae3e1d826f74d5c7b803925f90ba8253ed9af0879d15a5c8372d8230832203
Tx public key: c970985e875b50d9113a1e93d639c087923799287f8f856d907882bab8356e2d
Timestamp: 1764093921 Timestamp [UTC]: 2025-11-25 18:05:21 Age [y:d:h:m:s]: 00:361:03:08:07
Block: 1419990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263504 RingCT/type: yes/0
Extra: 01c970985e875b50d9113a1e93d639c087923799287f8f856d907882bab8356e2d021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a3c34eb14499ac1e179b041eecd95e162da3f084e1704706324f5b7dab795728 0.000600000000 1908531 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 dinastycoin-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": 1420000, "vin": [ { "gen": { "height": 1419990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3c34eb14499ac1e179b041eecd95e162da3f084e1704706324f5b7dab795728" } } ], "extra": [ 1, 201, 112, 152, 94, 135, 91, 80, 217, 17, 58, 30, 147, 214, 57, 192, 135, 146, 55, 153, 40, 127, 143, 133, 109, 144, 120, 130, 186, 184, 53, 110, 45, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: