← previous blocknext block →recent activity
Analyzing
Block #87,304,358
13 transactions · 13 stateful · 2026-07-12 16:22:32 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,304,358 · 13 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
2w05w16w09w211w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe2c1082…db16
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0xfb0022d6…1264
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1f3ed4ba…9deb
0x34b655…2a6f
4 touches
1 conflict
0x22fc9794…6e93
0x34b655…2a6f
4 touches
1 conflict
0x4e068769…91ad
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 0xfe2c108297…2fdb16
Audit this contract →
← previous block·next block →recent activity