← previous blocknext block →recent activity
Analyzing
Block #96,437,839
8 transactions · 7 stateful · 2026-08-16 08:06:56 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,437,839 · 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0313aedc…bfaf
0x34b655…2a6f
2 touches
0 conflicts
0x17b720f5…ad7a
0x34b655…2a6f
2 touches
0 conflicts
0x18cf36a6…a3a3
0x34b655…2a6f
2 touches
0 conflicts
0x369883e3…a449
0x34b655…2a6f
2 touches
0 conflicts
0x3dcc92f2…f562
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
3 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity