← previous blocknext block →recent activity
Analyzing
Block #96,297,929
11 transactions · 7 stateful · 2026-08-15 20:23:17 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,297,929 · 11 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
2w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f60dbd0…5f36
0x34b655…2a6f
4 touches
1 conflict
0xa940f3a4…c5e7
0x34b655…2a6f
4 touches
1 conflict
0xa940f3a4…c5e8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x748ce49f…a12c
0x34b655…2a6f
4 touches
1 conflict
0x16aaf8c0…061e
0x34b655…2a6f
2 touches
0 conflicts
0x16f2b4e1…e98b
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 0x9f60dbd0e9…f55f36
Audit this contract →
← previous block·next block →recent activity