Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a42b6db472d02c9838c9f704c17acbc6ef8ee888b8b47a85ce405aba7f5f544f

Tx prefix hash: 9e809e1d9bcca77c91e3794f57d5f08fae04e975187c6b1d733435ba997b207c
Tx public key: 7dd24ac6be8a9870edb4aa85e6e58dafd62a680ee472bf493350d7ca879dd687
Timestamp: 1659776841 Timestamp [UTC]: 2022-08-06 09:07:21 Age [y:d:h:m:s]: 04:107:18:11:42
Block: 559859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1123268 RingCT/type: yes/0
Extra: 017dd24ac6be8a9870edb4aa85e6e58dafd62a680ee472bf493350d7ca879dd687021100000004aac913b7000000000000000000

1 output(s) for total of 0.008569487355 xmr

stealth address amount amount idx tag
00: 3252e5da53889378da6397efde77c45e5867d24ed40fde061306a7c8a120bec3 0.008569487355 992041 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": 559869, "vin": [ { "gen": { "height": 559859 } } ], "vout": [ { "amount": 8569487355, "target": { "key": "3252e5da53889378da6397efde77c45e5867d24ed40fde061306a7c8a120bec3" } } ], "extra": [ 1, 125, 210, 74, 198, 190, 138, 152, 112, 237, 180, 170, 133, 230, 229, 141, 175, 214, 42, 104, 14, 228, 114, 191, 73, 51, 80, 215, 202, 135, 157, 214, 135, 2, 17, 0, 0, 0, 4, 170, 201, 19, 183, 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: