Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7771bb47db4984b6f2ada3daf2b6deba9ebf19c4d89685590969ebe56d368f6e

Tx prefix hash: d4a8c77ec47dd9c9e08ecc3cd9d114dc8897906b5cc7e9ffd3514aa1d6b055f6
Tx public key: 0faf12a9aad3f273b928f3123f38c6f2e3dc14fe4d07ce71cbf7edf0f1c2d2e3
Timestamp: 1789426420 Timestamp [UTC]: 2026-09-14 22:53:40 Age [y:d:h:m:s]: 00:064:07:20:00
Block: 1635584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 45346 RingCT/type: yes/0
Extra: 010faf12a9aad3f273b928f3123f38c6f2e3dc14fe4d07ce71cbf7edf0f1c2d2e3

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 960240705e12e5602844ab12fb6d50c34c4a5dc3d6188357f9afddaaa3c1b636 0.000600000000 2125614 of 15 <0b>

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": 1635594, "vin": [ { "gen": { "height": 1635584 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "960240705e12e5602844ab12fb6d50c34c4a5dc3d6188357f9afddaaa3c1b636", "view_tag": "0b" } } } ], "extra": [ 1, 15, 175, 18, 169, 170, 211, 242, 115, 185, 40, 243, 18, 63, 56, 198, 242, 227, 220, 20, 254, 77, 7, 206, 113, 203, 247, 237, 240, 241, 194, 210, 227 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: