← previous blocknext block →recent activity
Analyzing
Block #87,341,388
8 transactions · 6 stateful · 2026-07-12 20:30:10 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,341,388 · 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b8b3363…6632
0x34b655…2a6f
4 touches
1 conflict
0x4b8b3363…6633
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xd2171a4a…a036
0x34b655…2a6f
4 touches
1 conflict
0xe85e763f…3b25
0x34b655…2a6f
4 touches
1 conflict
0x263aa68b…6c6a
0x34b655…2a6f
2 touches
0 conflicts
0x2b96adb2…ba5d
0x34b655…2a6f
2 touches
0 conflicts
0x2ddad553…f810
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 0x4b8b336399…e06632
Audit this contract →
← previous block·next block →recent activity