Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5009bca34af7ca88186cb5be11cd7c9544e394056beee88b728ed6db1e8d276

Tx prefix hash: 3b94a008a7cd9a5fb26044a7f71b0f5059c0f5f986dc9ce16e029aeea52f37dc
Tx public key: 64505a57f9b86bd9bde9edefed9f1b120b4ada4db7659d56e3b2d296b8f7e407
Timestamp: 1748973344 Timestamp [UTC]: 2025-06-03 17:55:44 Age [y:d:h:m:s]: 00:346:22:26:11
Block: 1297214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237999 RingCT/type: yes/0
Extra: 0164505a57f9b86bd9bde9edefed9f1b120b4ada4db7659d56e3b2d296b8f7e407021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f4e68895d02faef739738af95b0bd4b7ffe731cb5a82e45a89be8f8a51ac517c 0.000600000000 1784731 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": 1297224, "vin": [ { "gen": { "height": 1297214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4e68895d02faef739738af95b0bd4b7ffe731cb5a82e45a89be8f8a51ac517c" } } ], "extra": [ 1, 100, 80, 90, 87, 249, 184, 107, 217, 189, 233, 237, 239, 237, 159, 27, 18, 11, 74, 218, 77, 183, 101, 157, 86, 227, 178, 210, 150, 184, 247, 228, 7, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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: