Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b332f94d0d30e1b03f339f54f6bbdd0f7f3dee4089f04ab44ba21d895706de0

Tx prefix hash: b220d65d262a8461b9554331c0d5356c15d208ca0079c379832c63713361c44f
Tx public key: 095742d5335801a1548c134b34e94d27d91a3d34f67195c827e134d9ec616f34
Timestamp: 1763284973 Timestamp [UTC]: 2025-11-16 09:22:53 Age [y:d:h:m:s]: 01:005:10:20:16
Block: 1413280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270214 RingCT/type: yes/0
Extra: 01095742d5335801a1548c134b34e94d27d91a3d34f67195c827e134d9ec616f340211000000024e7bfc09000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bb8808ff00205e40cad26442a5866070dc5c717f4389ecc8825b267dbe962ca1 0.000600000000 1901759 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": 1413290, "vin": [ { "gen": { "height": 1413280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb8808ff00205e40cad26442a5866070dc5c717f4389ecc8825b267dbe962ca1" } } ], "extra": [ 1, 9, 87, 66, 213, 51, 88, 1, 161, 84, 140, 19, 75, 52, 233, 77, 39, 217, 26, 61, 52, 246, 113, 149, 200, 39, 225, 52, 217, 236, 97, 111, 52, 2, 17, 0, 0, 0, 2, 78, 123, 252, 9, 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: