Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0814339642b8337d9670e4809a8d00e00ab2ce575a6a91e8742e2d2e41d1a4d2

Tx prefix hash: 60dd8d4f0dc38f9ae4b3eab20dff484500efd21ec6ab63fb46c58e48ff96292f
Tx public key: c6e46fdde18058e8a388e7f62425a4cb50d6369b7d0bfb95a717adcf5be60ef8
Timestamp: 1791924900 Timestamp [UTC]: 2026-10-13 20:55:00 Age [y:d:h:m:s]: 00:030:09:39:34
Block: 1653800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 23409 RingCT/type: yes/0
Extra: 01c6e46fdde18058e8a388e7f62425a4cb50d6369b7d0bfb95a717adcf5be60ef8

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ff97f40b8b8ae3b835572a9edc52a8fe13e53258e02ff1ca8279a6b80fd603f3 0.000600000000 2143956 of 15 <e7>

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": 1653810, "vin": [ { "gen": { "height": 1653800 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "ff97f40b8b8ae3b835572a9edc52a8fe13e53258e02ff1ca8279a6b80fd603f3", "view_tag": "e7" } } } ], "extra": [ 1, 198, 228, 111, 221, 225, 128, 88, 232, 163, 136, 231, 246, 36, 37, 164, 203, 80, 214, 54, 155, 125, 11, 251, 149, 167, 23, 173, 207, 91, 230, 14, 248 ], "rct_signatures": { "type": 0 } }


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