← previous blocknext block →recent activity
Analyzing
Block #93,367,512
16 transactions · 16 stateful · 2026-08-05 14:11:30 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.44
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,367,512 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w39w410w511w612w615w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x41f1e2e5…2edf
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xfbe9c95e…de7c
0x34b655…2a6f
6 touches
3 conflicts
0xc3236f63…06c1
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xa6b48d6e…0705
0x34b655…2a6f
6 touches
3 conflicts
0xe3684e08…c96a
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity