Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f7f95c1aabf6aa2e823fd31cd010ffcd71513a9de185876e572a6496cb334ff

Tx prefix hash: 77f51f6bb6c27e73cb5c34f8cfe9bbe13ab2e06bf6f8ca2ff5bc54d0cd3f3f9a
Tx public key: a534446ab1aa2c8daba9bad6d36bf5a38110a793ce4cfe07e8249b3fa0ca0bb1
Timestamp: 1767838588 Timestamp [UTC]: 2026-01-08 02:16:28 Age [y:d:h:m:s]: 00:315:22:22:00
Block: 1451027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231243 RingCT/type: yes/0
Extra: 01a534446ab1aa2c8daba9bad6d36bf5a38110a793ce4cfe07e8249b3fa0ca0bb102110000001b215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aed7c478c2583dee420c253e1b7d08a6c19a2bbca83796cb2479cc497c9dd0d3 0.000600000000 1940033 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": 1451037, "vin": [ { "gen": { "height": 1451027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aed7c478c2583dee420c253e1b7d08a6c19a2bbca83796cb2479cc497c9dd0d3" } } ], "extra": [ 1, 165, 52, 68, 106, 177, 170, 44, 141, 171, 169, 186, 214, 211, 107, 245, 163, 129, 16, 167, 147, 206, 76, 254, 7, 232, 36, 155, 63, 160, 202, 11, 177, 2, 17, 0, 0, 0, 27, 33, 91, 191, 137, 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: