← previous blocknext block →recent activity
Analyzing
Block #96,039,241
8 transactions · 6 stateful · 2026-08-14 22:42:08 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,039,241 · 8 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
2w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b49b083…91d8
0x34b655…2a6f
4 touches
1 conflict
0xa46242d8…c0a8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0494220d…abf6
0x34b655…2a6f
2 touches
0 conflicts
0x0494220d…abf7
0x34b655…2a6f
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x168f7615…a8dd
0x34b655…2a6f
2 touches
0 conflicts
0x168f7615…a8de
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 0x1b49b08350…b291d8
Audit this contract →
← previous block·next block →recent activity