Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06f05c12709a218ca5025dea5eef5477cf77f0d2bfe0203a485f1b37de3e76b1

Tx prefix hash: fb22fd4d2d2c0e549fc4859b048743b7a31bd1ad6d439087a7a3082aae5f328c
Tx public key: 24f41449ce2c85ca1e4570c3a01f443a1da31d3957f38b2469900f7639d27b2e
Timestamp: 1738198745 Timestamp [UTC]: 2025-01-30 00:59:05 Age [y:d:h:m:s]: 01:293:22:21:18
Block: 1208021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474208 RingCT/type: yes/0
Extra: 0124f41449ce2c85ca1e4570c3a01f443a1da31d3957f38b2469900f7639d27b2e021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5ecdc461170bb74da422e274d5a4cb839e75c9a29e2117e5fcc02e31621d2cfd 0.000600000000 1694748 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": 1208031, "vin": [ { "gen": { "height": 1208021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ecdc461170bb74da422e274d5a4cb839e75c9a29e2117e5fcc02e31621d2cfd" } } ], "extra": [ 1, 36, 244, 20, 73, 206, 44, 133, 202, 30, 69, 112, 195, 160, 31, 68, 58, 29, 163, 29, 57, 87, 243, 139, 36, 105, 144, 15, 118, 57, 210, 123, 46, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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: