Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9a2639e849a25af5bd0c850891181fafea2f80ceafd02c72444c44d0e5fa0d3

Tx prefix hash: a4007fe4dbd0f4ca5d322ed3c76bf1633546040fbfa4a5f1c44d2239336bb33a
Tx public key: 6ddb86bc41bf274ff7791f51c3960cb3e0c0e939753b89b1bfe25b19762ab1c0
Timestamp: 1744281326 Timestamp [UTC]: 2025-04-10 10:35:26 Age [y:d:h:m:s]: 01:137:04:21:44
Block: 1258356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362394 RingCT/type: yes/0
Extra: 016ddb86bc41bf274ff7791f51c3960cb3e0c0e939753b89b1bfe25b19762ab1c00211000000046c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7de11c3d992790101a7d294ae36aba3778dc802eaa242dbd8e502caa8b1935d2 0.000600000000 1745489 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": 1258366, "vin": [ { "gen": { "height": 1258356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7de11c3d992790101a7d294ae36aba3778dc802eaa242dbd8e502caa8b1935d2" } } ], "extra": [ 1, 109, 219, 134, 188, 65, 191, 39, 79, 247, 121, 31, 81, 195, 150, 12, 179, 224, 192, 233, 57, 117, 59, 137, 177, 191, 226, 91, 25, 118, 42, 177, 192, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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: