Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e94a9bb2f418356fc7b087e0a04029f802fa8e812835b7d9a1d283e91e362b4

Tx prefix hash: 065a5b94aadc437001dcc317b4690591e30aa5c7bdae35126e73e49a23c56615
Tx public key: 1669b459f1ebe8dfab3dab1dc9c15ef07d20976572cabc60add57d48af04acec
Timestamp: 1743691578 Timestamp [UTC]: 2025-04-03 14:46:18 Age [y:d:h:m:s]: 01:229:21:46:51
Block: 1253473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428410 RingCT/type: yes/0
Extra: 011669b459f1ebe8dfab3dab1dc9c15ef07d20976572cabc60add57d48af04acec021100000005a2ed016b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d0ae09bf3901db51dd8512ebe72933270b969d3f8a19842752fcc76774d68a40 0.000600000000 1740554 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": 1253483, "vin": [ { "gen": { "height": 1253473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0ae09bf3901db51dd8512ebe72933270b969d3f8a19842752fcc76774d68a40" } } ], "extra": [ 1, 22, 105, 180, 89, 241, 235, 232, 223, 171, 61, 171, 29, 201, 193, 94, 240, 125, 32, 151, 101, 114, 202, 188, 96, 173, 213, 125, 72, 175, 4, 172, 236, 2, 17, 0, 0, 0, 5, 162, 237, 1, 107, 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: