Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d51b2bb71ee0d710495ad6ca9e72bcc681c6e789beb32a99d0eb8385d81db3dd

Tx prefix hash: 0a87d35eecf5ad2e3dfabbea5148bb77398ad50cbb42ae62f6060f0d8db77a6d
Tx public key: dbe9db156cc94290bf0f8fb2f02ca63025701d14b9f482077a46ef0ec98bd336
Timestamp: 1739994237 Timestamp [UTC]: 2025-02-19 19:43:57 Age [y:d:h:m:s]: 01:275:16:26:25
Block: 1222842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460652 RingCT/type: yes/0
Extra: 01dbe9db156cc94290bf0f8fb2f02ca63025701d14b9f482077a46ef0ec98bd336021100000005007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4b0026aefc47d172a284fe23f1594be016a1549507acc63d8ccac04161f9f804 0.000600000000 1709697 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": 1222852, "vin": [ { "gen": { "height": 1222842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b0026aefc47d172a284fe23f1594be016a1549507acc63d8ccac04161f9f804" } } ], "extra": [ 1, 219, 233, 219, 21, 108, 201, 66, 144, 191, 15, 143, 178, 240, 44, 166, 48, 37, 112, 29, 20, 185, 244, 130, 7, 122, 70, 239, 14, 201, 139, 211, 54, 2, 17, 0, 0, 0, 5, 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: