← previous blocknext block →recent activity
Analyzing
Block #87,623,931
16 transactions · 14 stateful · 2026-07-14 04:00:30 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,623,931 · 16 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
1w02w16w07w08w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x588c5b6a…60d2
0x34b655…2a6f
4 touches
1 conflict
0x89cb869a…08a6
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xc75664ed…ea73
0x34b655…2a6f
4 touches
1 conflict
0xc75664ed…ea74
0x34b655…2a6f
4 touches
1 conflict
0xebf6cfe3…441e
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
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 0x588c5b6adb…3060d2
Audit this contract →
← previous block·next block →recent activity