← previous blocknext block →recent activity
Analyzing
Block #96,289,621
8 transactions · 8 stateful · 2026-08-15 19:41:30 UTC
Parallelism
38/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,289,621 · 8 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb50e0c79…2164
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x3727225e…a3cf
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xe236ed33…4a3c
0x34b655…2a6f
4 touches
1 conflict
0xe999cbf5…d18a
0x34b655…2a6f
4 touches
1 conflict
0x733a5000…6e67
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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 0xb50e0c7942…0b2164
Audit this contract →
← previous block·next block →recent activity