Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e45fd28a0198d25b0eeb0555145efef0567efb2ccb730588d74812ba4ba561e

Tx prefix hash: 93c81d0f74ef0e22c2f330509630c34994a6a912e8d2a22988945a350385f218
Tx public key: ee52ab3a4524ebf9fbd4b7a9be2da41e66ec78ce43c3cf37210cfc541986020d
Timestamp: 1634508420 Timestamp [UTC]: 2021-10-17 22:07:00 Age [y:d:h:m:s]: 04:206:17:42:12
Block: 355175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1176354 RingCT/type: yes/0
Extra: 01ee52ab3a4524ebf9fbd4b7a9be2da41e66ec78ce43c3cf37210cfc541986020d0211000000054a0f5013000000000000000000

1 output(s) for total of 0.040848205231 xmr

stealth address amount amount idx tag
00: c0919105f0c01e14952152e0a3f47e7637c22d9ca0a90e88403047304e0dbb51 0.040848205231 725231 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": 355185, "vin": [ { "gen": { "height": 355175 } } ], "vout": [ { "amount": 40848205231, "target": { "key": "c0919105f0c01e14952152e0a3f47e7637c22d9ca0a90e88403047304e0dbb51" } } ], "extra": [ 1, 238, 82, 171, 58, 69, 36, 235, 249, 251, 212, 183, 169, 190, 45, 164, 30, 102, 236, 120, 206, 67, 195, 207, 55, 33, 12, 252, 84, 25, 134, 2, 13, 2, 17, 0, 0, 0, 5, 74, 15, 80, 19, 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: