Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a84a2c8a30bde60381e88609edf330e9a763bd7328a26cc5c3f0b7a4df2cff30

Tx prefix hash: 94084cb63ae0246b03ae48dbd014e29d287ea224ed5094bda361292def396635
Tx public key: f5c3e4871b02e37b85e082c800880597dbeca0826f1bcca8c876a515e2fe6f3c
Timestamp: 1775220885 Timestamp [UTC]: 2026-04-03 12:54:45 Age [y:d:h:m:s]: 00:224:18:45:57
Block: 1511955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166032 RingCT/type: yes/0
Extra: 01f5c3e4871b02e37b85e082c800880597dbeca0826f1bcca8c876a515e2fe6f3c021100000001e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 489d428fab972bc873304a90fad1cd65e868a56c4e8f6235eda251505b24f1ef 0.000600000000 2001751 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": 1511965, "vin": [ { "gen": { "height": 1511955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "489d428fab972bc873304a90fad1cd65e868a56c4e8f6235eda251505b24f1ef" } } ], "extra": [ 1, 245, 195, 228, 135, 27, 2, 227, 123, 133, 224, 130, 200, 0, 136, 5, 151, 219, 236, 160, 130, 111, 27, 204, 168, 200, 118, 165, 21, 226, 254, 111, 60, 2, 17, 0, 0, 0, 1, 227, 215, 220, 159, 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: