← previous blocknext block →recent activity
Analyzing
Block #96,293,815
19 transactions · 17 stateful · 2026-08-15 20:02:36 UTC
Parallelism
84/100
Blocked
35%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,293,815 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w211w012w113w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9210e826…1414
0x34b655…2a6f
6 touches
3 conflicts
0x5adda4a7…b840
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xe561281f…7569
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
3 conflicts on slot 0x9210e826c8…c41414
Audit this contract →
← previous block·next block →recent activity