← previous blocknext block →recent activity
Analyzing
Block #87,628,933
16 transactions · 14 stateful · 2026-07-14 04:33:59 UTC
Parallelism
63/100
Blocked
57%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,628,933 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w06w18w29w310w311w412w514w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96efe05d…5d48
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xed4604d7…11d2
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x6323c5ea…ce8a
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
10 conflicts on slot 0x96efe05d27…da5d48
Audit this contract →
← previous block·next block →recent activity