Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26ad41cbe84a38be81603df62367fefa1621417453fa53e60c384db8059e1edf

Tx prefix hash: f32704d4561dfafc5eb4d6d8d3ea3139b34b4866c6688d8e83e500f216250b6e
Tx public key: 998d99c6b30f8d28a1767fdc0dd2048eb0c2d0c85833469f04dc623b84f05394
Timestamp: 1773800398 Timestamp [UTC]: 2026-03-18 02:19:58 Age [y:d:h:m:s]: 00:249:05:30:26
Block: 1500185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183309 RingCT/type: yes/0
Extra: 01998d99c6b30f8d28a1767fdc0dd2048eb0c2d0c85833469f04dc623b84f05394021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d83f6cea3efb674c24341cf4aa64abe20e3d8fdb80481f0ea3a5c0a0d083439b 0.000600000000 1989855 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": 1500195, "vin": [ { "gen": { "height": 1500185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d83f6cea3efb674c24341cf4aa64abe20e3d8fdb80481f0ea3a5c0a0d083439b" } } ], "extra": [ 1, 153, 141, 153, 198, 179, 15, 141, 40, 161, 118, 127, 220, 13, 210, 4, 142, 176, 194, 208, 200, 88, 51, 70, 159, 4, 220, 98, 59, 132, 240, 83, 148, 2, 17, 0, 0, 0, 4, 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: