Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 603ccc17ca5f9c21ee3d465753c7b7f3fa4eb1eeb19c340d054f5f0ae556c2ee

Tx prefix hash: 2c7323a00a6d1b4732890b891c92dfbd6007504a13ba08838ad8cda3474063b3
Tx public key: cec77965eb2c3775334a50a96ec00e336b5afa5481eb75018054617175edfdfb
Timestamp: 1657309916 Timestamp [UTC]: 2022-07-08 19:51:56 Age [y:d:h:m:s]: 04:137:00:23:19
Block: 539536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1143958 RingCT/type: yes/0
Extra: 01cec77965eb2c3775334a50a96ec00e336b5afa5481eb75018054617175edfdfb02110000000ecb8520c2000000000000000000

1 output(s) for total of 0.010006758241 xmr

stealth address amount amount idx tag
00: ed96cddb25e88d1a5126597ae34a901862d2c7859b8777d0ca0cd1a7f7f1de85 0.010006758241 969649 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": 539546, "vin": [ { "gen": { "height": 539536 } } ], "vout": [ { "amount": 10006758241, "target": { "key": "ed96cddb25e88d1a5126597ae34a901862d2c7859b8777d0ca0cd1a7f7f1de85" } } ], "extra": [ 1, 206, 199, 121, 101, 235, 44, 55, 117, 51, 74, 80, 169, 110, 192, 14, 51, 107, 90, 250, 84, 129, 235, 117, 1, 128, 84, 97, 113, 117, 237, 253, 251, 2, 17, 0, 0, 0, 14, 203, 133, 32, 194, 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: