Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b39b798a38e5521fedae8ef54c0d3bbb4b094dbfe1fd1689b5c4846217951b7

Tx prefix hash: 370280acf9bdd0d60fe7dc2f7aaed87f12826f9123d333a3e7c8ccacdd33324b
Tx public key: 1d5a0850cbb1fbef45864f53385c2622bb0231e8efb79d8f5b2fac884a816b72
Timestamp: 1575680723 Timestamp [UTC]: 2019-12-07 01:05:23 Age [y:d:h:m:s]: 06:352:03:30:00
Block: 22138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0967 kB
Tx version: 2 No of confirmations: 1661356 RingCT/type: yes/0
Extra: 011d5a0850cbb1fbef45864f53385c2622bb0231e8efb79d8f5b2fac884a816b72020d3930303100010000002f90824d

1 output(s) for total of 0.518380301426 xmr

stealth address amount amount idx tag
00: ac057a9d69b16f07fdf582d2dfa895aa82e0ae24253e0df05c1d360d7ab79709 0.518380301426 35059 of 0 -

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": 22148, "vin": [ { "gen": { "height": 22138 } } ], "vout": [ { "amount": 518380301426, "target": { "key": "ac057a9d69b16f07fdf582d2dfa895aa82e0ae24253e0df05c1d360d7ab79709" } } ], "extra": [ 1, 29, 90, 8, 80, 203, 177, 251, 239, 69, 134, 79, 83, 56, 92, 38, 34, 187, 2, 49, 232, 239, 183, 157, 143, 91, 47, 172, 136, 74, 129, 107, 114, 2, 13, 57, 48, 48, 49, 0, 1, 0, 0, 0, 47, 144, 130, 77 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: