Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 345dd284cc06cb92afc40d749886fc33bae7446964afc6fa60f803534a2b72ae

Tx prefix hash: 182425b4c98c8d5becc447a988bfe73c52f2c3a5ce52fb29dc6310c8806aeb33
Tx public key: f60848295f216495d17c68f8b654767fe6533ad67e57ec45b470bd1b96149054
Timestamp: 1774167101 Timestamp [UTC]: 2026-03-22 08:11:41 Age [y:d:h:m:s]: 00:244:22:05:56
Block: 1503215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180279 RingCT/type: yes/0
Extra: 01f60848295f216495d17c68f8b654767fe6533ad67e57ec45b470bd1b96149054021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e4a8b3e631be9a48419d021cc40687eb978d1c8661550284ead31f4c48ece1e3 0.000600000000 1992921 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": 1503225, "vin": [ { "gen": { "height": 1503215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4a8b3e631be9a48419d021cc40687eb978d1c8661550284ead31f4c48ece1e3" } } ], "extra": [ 1, 246, 8, 72, 41, 95, 33, 100, 149, 209, 124, 104, 248, 182, 84, 118, 127, 230, 83, 58, 214, 126, 87, 236, 69, 180, 112, 189, 27, 150, 20, 144, 84, 2, 17, 0, 0, 0, 5, 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: