Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c01134c2684f4f7f6fa9355d742e428f746bb4ab7b06de40cc22170558a28d0

Tx prefix hash: cf1a47d2c1a3483f064bfc98c56940bd31eddcfffdcd6249d4b4de5e76ec495c
Tx public key: 67381e12a188080cb1b24342e7881c24ebd713a1eec9c25dea4a9f8700e926f8
Timestamp: 1780155264 Timestamp [UTC]: 2026-05-30 15:34:24 Age [y:d:h:m:s]: 00:169:03:15:59
Block: 1546980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 132110 RingCT/type: yes/0
Extra: 0167381e12a188080cb1b24342e7881c24ebd713a1eec9c25dea4a9f8700e926f8

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 86bb500dbeae38d3943b4cf34856e59880a05ea9d81d36bfb3ca455a31534242 0.000600000000 2036954 of 15 <4c>

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": 1546990, "vin": [ { "gen": { "height": 1546980 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "86bb500dbeae38d3943b4cf34856e59880a05ea9d81d36bfb3ca455a31534242", "view_tag": "4c" } } } ], "extra": [ 1, 103, 56, 30, 18, 161, 136, 8, 12, 177, 178, 67, 66, 231, 136, 28, 36, 235, 215, 19, 161, 238, 201, 194, 93, 234, 74, 159, 135, 0, 233, 38, 248 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: