Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a3505631db3f58fbff4e81690b1b7f217bfdc34d516fce4e79fbb539d04cd0a

Tx prefix hash: 61eb999e1ea4088841e59fad94c56b037da72a0928c9d7f9f70c3e7ee75d31c2
Tx public key: 2d08ffae76dbb11edce0eddce1e50f238985e7f8d34137b46eefd4c41487bb7b
Timestamp: 1773992839 Timestamp [UTC]: 2026-03-20 07:47:19 Age [y:d:h:m:s]: 00:240:00:51:19
Block: 1501760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177015 RingCT/type: yes/0
Extra: 012d08ffae76dbb11edce0eddce1e50f238985e7f8d34137b46eefd4c41487bb7b021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a813a988ea531d034ea1d1be4494d5b73832b5bc3d53d5b06667bd3806deb2f5 0.000600000000 1991446 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": 1501770, "vin": [ { "gen": { "height": 1501760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a813a988ea531d034ea1d1be4494d5b73832b5bc3d53d5b06667bd3806deb2f5" } } ], "extra": [ 1, 45, 8, 255, 174, 118, 219, 177, 30, 220, 224, 237, 220, 225, 229, 15, 35, 137, 133, 231, 248, 211, 65, 55, 180, 110, 239, 212, 196, 20, 135, 187, 123, 2, 17, 0, 0, 0, 2, 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: