Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c1d1d040bc3bd7aa0bf48ce93626475d6ec4bbc66c23aab4ff44fa773d4fc0a

Tx prefix hash: 60789a3d4a9cb3f874de72752e2f4f09816ee20a3540efd5be673ba97497f20e
Tx public key: 40857ef5b4813f6cefba3fbf5148d2a356261ce1fd6444b5f09f8b99b30bc012
Timestamp: 1773382160 Timestamp [UTC]: 2026-03-13 06:09:20 Age [y:d:h:m:s]: 00:243:20:14:04
Block: 1496734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179576 RingCT/type: yes/0
Extra: 0140857ef5b4813f6cefba3fbf5148d2a356261ce1fd6444b5f09f8b99b30bc012021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7939a812db0f269fd284745de94145ecd2d7dffe9fb842bcbfbc7bb1baba9053 0.000600000000 1986362 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": 1496744, "vin": [ { "gen": { "height": 1496734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7939a812db0f269fd284745de94145ecd2d7dffe9fb842bcbfbc7bb1baba9053" } } ], "extra": [ 1, 64, 133, 126, 245, 180, 129, 63, 108, 239, 186, 63, 191, 81, 72, 210, 163, 86, 38, 28, 225, 253, 100, 68, 181, 240, 159, 139, 153, 179, 11, 192, 18, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: