← previous blocknext block →recent activity
Analyzing
Block #96,132,642
20 transactions · 18 stateful · 2026-08-15 06:31:57 UTC
Parallelism
90/100
Blocked
11%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,132,642 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w08w113w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0xb6aedce9…a483
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x3f24a8ec…24e1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x831e2e85…6eab
0x34b655…2a6f
2 touches
0 conflicts
0x87292c3e…5e25
0x34b655…2a6f
2 touches
0 conflicts
0xa01f2285…f16f
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xea1b8c07ee…d0b969
Audit this contract →
← previous block·next block →recent activity