← previous blocknext block →recent activity
Analyzing
Block #87,318,544
23 transactions · 22 stateful · 2026-07-12 17:57:24 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,318,544 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w29w110w214w316w420w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x80fd3987…2314
0x34b655…2a6f
6 touches
3 conflicts
0x962c1ba3…249a
0xd32edf…ff58
5 touches
3 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
5 touches
3 conflicts
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0x3d4584df…ffed
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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity