Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b16a96f27881ad3ccc84f56a7644185a6bfdd30dcb3d2fdc1bdcf0d7e7c4673a

Tx prefix hash: a5aa5d78d1a7db7300e30194911eb5a246eb120d19b7af8b96d27d1c0117344e
Tx public key: 591ead431e037285032de066230253a16186e5b129ecddf813ff34f24a7417f1
Timestamp: 1759540694 Timestamp [UTC]: 2025-10-04 01:18:14 Age [y:d:h:m:s]: 01:043:15:09:20
Block: 1382253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297516 RingCT/type: yes/0
Extra: 01591ead431e037285032de066230253a16186e5b129ecddf813ff34f24a7417f1021100000002a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9b1c032c55552c7d133d889434ce40f5d0800af84228c8c757534990c8d3df51 0.000600000000 1870388 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": 1382263, "vin": [ { "gen": { "height": 1382253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b1c032c55552c7d133d889434ce40f5d0800af84228c8c757534990c8d3df51" } } ], "extra": [ 1, 89, 30, 173, 67, 30, 3, 114, 133, 3, 45, 224, 102, 35, 2, 83, 161, 97, 134, 229, 177, 41, 236, 221, 248, 19, 255, 52, 242, 74, 116, 23, 241, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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: