Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 518d3e4ee72dd921517294a910908f3c7fec4af1f02b327b6eeef4e4660a1e6d

Tx prefix hash: 259717dac6cd001063ae3692c8ff2de56d29d5e24bf3758cb66302cbeb0231ea
Tx public key: 57a085667ec94dee1f90d4bd4d86ad613b5594d6bcfcfabf104a2d2fa8a6f327
Timestamp: 1651997217 Timestamp [UTC]: 2022-05-08 08:06:57 Age [y:d:h:m:s]: 04:009:06:53:21
Block: 496650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1038522 RingCT/type: yes/0
Extra: 0157a085667ec94dee1f90d4bd4d86ad613b5594d6bcfcfabf104a2d2fa8a6f327021100000007cb8520c2000000000000000000

1 output(s) for total of 0.013880099878 xmr

stealth address amount amount idx tag
00: 6271fcbc947ddc7e4e7158e225941749ca1030c85ea97073a63505b9a6411bdd 0.013880099878 920637 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": 496660, "vin": [ { "gen": { "height": 496650 } } ], "vout": [ { "amount": 13880099878, "target": { "key": "6271fcbc947ddc7e4e7158e225941749ca1030c85ea97073a63505b9a6411bdd" } } ], "extra": [ 1, 87, 160, 133, 102, 126, 201, 77, 238, 31, 144, 212, 189, 77, 134, 173, 97, 59, 85, 148, 214, 188, 252, 250, 191, 16, 74, 45, 47, 168, 166, 243, 39, 2, 17, 0, 0, 0, 7, 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: