Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 022c6916a6ad5a17b3e3290521728da42e4f48fccb91e901a1df291894902496

Tx prefix hash: 206cc5f64447584d048e8f2aa2b3c94c7797c8b374e7fc06f3cb3b0f121bd9ee
Tx public key: 6e20d84960ce661a7427ea43f3bf46422ec51693c15435c01d388c2056f8056d
Timestamp: 1764422819 Timestamp [UTC]: 2025-11-29 13:26:59 Age [y:d:h:m:s]: 00:349:04:42:26
Block: 1422716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254853 RingCT/type: yes/0
Extra: 016e20d84960ce661a7427ea43f3bf46422ec51693c15435c01d388c2056f8056d021100000004da554848000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 01abd788dbcc2d400e4a42affb1a02b841170d1a37b8b5618eb4a967d0c448c5 0.000600000000 1911289 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": 1422726, "vin": [ { "gen": { "height": 1422716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01abd788dbcc2d400e4a42affb1a02b841170d1a37b8b5618eb4a967d0c448c5" } } ], "extra": [ 1, 110, 32, 216, 73, 96, 206, 102, 26, 116, 39, 234, 67, 243, 191, 70, 66, 46, 197, 22, 147, 193, 84, 53, 192, 29, 56, 140, 32, 86, 248, 5, 109, 2, 17, 0, 0, 0, 4, 218, 85, 72, 72, 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: