Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f31d128a7b13c9b7b9c33dbd44db41be460581aa22fc432433d19ea48483d0ee

Tx prefix hash: fc22122fd7741791c53b0fdbaa32602c74ded3c820fd38fcf8c20bc6c59d80b4
Tx public key: e0e5449770366895a5a535ddbeccbda1d38d2ce6aee08952498611707bdbd7c3
Timestamp: 1704034497 Timestamp [UTC]: 2023-12-31 14:54:57 Age [y:d:h:m:s]: 02:326:02:23:07
Block: 925188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 758306 RingCT/type: yes/0
Extra: 01e0e5449770366895a5a535ddbeccbda1d38d2ce6aee08952498611707bdbd7c30211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fc288fab5a95cf750b230fc404c48e880f89ed27eebdda07bfbd451aec0f60fd 0.000600000000 1382948 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": 925198, "vin": [ { "gen": { "height": 925188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc288fab5a95cf750b230fc404c48e880f89ed27eebdda07bfbd451aec0f60fd" } } ], "extra": [ 1, 224, 229, 68, 151, 112, 54, 104, 149, 165, 165, 53, 221, 190, 204, 189, 161, 211, 141, 44, 230, 174, 224, 137, 82, 73, 134, 17, 112, 123, 219, 215, 195, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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: