Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fddde9f26e2741a891f18883d7b87fad3fa4fc4e97fe62b821261a613eaa7f74

Tx prefix hash: ede924ef37e16b595a1f524b82274049aa1f9b9e88da8f564da644b18d4e5ad4
Tx public key: ccb7cb9129ab515460099bca8e6c1be072496c659ca07dfb6bd8ab2a95639cb4
Timestamp: 1750902436 Timestamp [UTC]: 2025-06-26 01:47:16 Age [y:d:h:m:s]: 01:006:00:26:40
Block: 1312881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254023 RingCT/type: yes/0
Extra: 01ccb7cb9129ab515460099bca8e6c1be072496c659ca07dfb6bd8ab2a95639cb40211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c77ca3d340a1aa1a5e02032af85acc354a9b47c93586275d13b38c270dcf9d2f 0.000600000000 1800518 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": 1312891, "vin": [ { "gen": { "height": 1312881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c77ca3d340a1aa1a5e02032af85acc354a9b47c93586275d13b38c270dcf9d2f" } } ], "extra": [ 1, 204, 183, 203, 145, 41, 171, 81, 84, 96, 9, 155, 202, 142, 108, 27, 224, 114, 73, 108, 101, 156, 160, 125, 251, 107, 216, 171, 42, 149, 99, 156, 180, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: