Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f18acece5d6185ec66f5600f2f4ecfcc4c08b19953d39994bc04bd0de23d434

Tx prefix hash: 556ec88367021548dcb8fe112700daafcebbd3b43ef090636fe663bcc28b1554
Tx public key: 72e893d9f71cffe214daf839d506e33a66d21d64f7f5389dab48df150a5f3df4
Timestamp: 1657322733 Timestamp [UTC]: 2022-07-08 23:25:33 Age [y:d:h:m:s]: 03:314:06:12:46
Block: 539643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 996798 RingCT/type: yes/0
Extra: 0172e893d9f71cffe214daf839d506e33a66d21d64f7f5389dab48df150a5f3df4021100000003d3fcec30000000000000000000

1 output(s) for total of 0.009998592574 xmr

stealth address amount amount idx tag
00: 69a03975e5155bafc5816a91d01b12aa63f9f98bb087cb2b0d191b81eb97c0e3 0.009998592574 969790 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": 539653, "vin": [ { "gen": { "height": 539643 } } ], "vout": [ { "amount": 9998592574, "target": { "key": "69a03975e5155bafc5816a91d01b12aa63f9f98bb087cb2b0d191b81eb97c0e3" } } ], "extra": [ 1, 114, 232, 147, 217, 247, 28, 255, 226, 20, 218, 248, 57, 213, 6, 227, 58, 102, 210, 29, 100, 247, 245, 56, 157, 171, 72, 223, 21, 10, 95, 61, 244, 2, 17, 0, 0, 0, 3, 211, 252, 236, 48, 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: