← previous blocknext block →recent activity
Analyzing
Block #96,340,852
8 transactions · 8 stateful · 2026-08-15 23:59:10 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,340,852 · 8 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c3d51a9…db35
0x34b655…2a6f
4 touches
1 conflict
0x7c3d51a9…db36
0x34b655…2a6f
4 touches
1 conflict
0xf5b23754…5eb1
0x34b655…2a6f
4 touches
1 conflict
0x2fc6a7aa…b4f4
0x34b655…2a6f
4 touches
1 conflict
0x541021b0…93b9
0x065c9d…c394
2 touches
0 conflicts
0xbcb95663…14bd
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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 0x7c3d51a962…59db35
Audit this contract →
← previous block·next block →recent activity