← previous blocknext block →recent activity
Analyzing
Block #87,259,257
13 transactions · 11 stateful · 2026-07-12 11:21:02 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,259,257 · 13 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
1w02w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f93d576…f1de
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x09869760…4a94
0x40c49f…2af0
2 touches
0 conflicts
0x21241d27…8a8e
0x40c49f…2af0
2 touches
0 conflicts
0x8c7bb7a1…253b
0x40c49f…2af0
2 touches
0 conflicts
0xf874f053…c8f2
0x40c49f…2af0
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 0x3f93d57650…bff1de
Audit this contract →
← previous block·next block →recent activity