Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 355f3885c553dbfb4b5b2f77d9bed43cc40b21a079f92a081ad238fb52ddf347

Tx prefix hash: 9311fa9a21907fb5f556480a4c0bd60adbb5c0cc719e337b294770ecf15febf0
Tx public key: fab06332eb5d3abb582439f610fc82b6df9471ce18751c09ba6d11c2233d2bf0
Timestamp: 1757709822 Timestamp [UTC]: 2025-09-12 20:43:42 Age [y:d:h:m:s]: 00:345:05:31:58
Block: 1367076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252556 RingCT/type: yes/0
Extra: 01fab06332eb5d3abb582439f610fc82b6df9471ce18751c09ba6d11c2233d2bf0021100000009b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 468f01973661737cfdadc2acf6c639fd72d117f7dfa9d6bc5647e54071ef04d8 0.000600000000 1855115 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": 1367086, "vin": [ { "gen": { "height": 1367076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "468f01973661737cfdadc2acf6c639fd72d117f7dfa9d6bc5647e54071ef04d8" } } ], "extra": [ 1, 250, 176, 99, 50, 235, 93, 58, 187, 88, 36, 57, 246, 16, 252, 130, 182, 223, 148, 113, 206, 24, 117, 28, 9, 186, 109, 17, 194, 35, 61, 43, 240, 2, 17, 0, 0, 0, 9, 178, 247, 132, 196, 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: