← previous blocknext block →recent activity
Analyzing
Block #87,626,326
14 transactions · 12 stateful · 2026-07-14 04:16:31 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,626,326 · 14 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
1w02w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38b61269…48d7
0x34b655…2a6f
4 touches
1 conflict
0x3ca9a061…1f41
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x99c46e97…c1b2
0x34b655…2a6f
4 touches
1 conflict
0xed4604d7…11d2
0x34b655…2a6f
4 touches
1 conflict
0xf0ad9713…5796
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x38b61269d3…c048d7
Audit this contract →
← previous block·next block →recent activity