Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fa9c88fbfa4d2b6e44ad9f91423d4ec4a3bc87f1659d9d3abfda5aefe089ed1

Tx prefix hash: abb9372eaa137802685215147900c20a73492faf44404183abe6265b6f5672d8
Tx public key: 009ab25e8b2553372775427755a4c41e89f5619f95ff83d19ad474f9a6f986c8
Timestamp: 1772981680 Timestamp [UTC]: 2026-03-08 14:54:40 Age [y:d:h:m:s]: 00:258:00:49:11
Block: 1493438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190056 RingCT/type: yes/0
Extra: 01009ab25e8b2553372775427755a4c41e89f5619f95ff83d19ad474f9a6f986c8021100000008f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 225c074551bcc0aec71e0d265ba7e320ec451e7d6f1754ef64fe2eb7c2ad197d 0.000600000000 1982998 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": 1493448, "vin": [ { "gen": { "height": 1493438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "225c074551bcc0aec71e0d265ba7e320ec451e7d6f1754ef64fe2eb7c2ad197d" } } ], "extra": [ 1, 0, 154, 178, 94, 139, 37, 83, 55, 39, 117, 66, 119, 85, 164, 196, 30, 137, 245, 97, 159, 149, 255, 131, 209, 154, 212, 116, 249, 166, 249, 134, 200, 2, 17, 0, 0, 0, 8, 241, 136, 200, 168, 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: