← previous blocknext block →recent activity
Analyzing
Block #87,503,817
37 transactions · 27 stateful · 2026-07-13 14:36:25 UTC
Parallelism
84/100
Blocked
56%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,503,817 · 37 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
4w05w16w07w18w218w119w220w323w224w325w427w329w030w131w234w335w436w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3688185…9b36
0x34b655…2a6f
8 touches
6 conflicts
0x767799cd…f423
0xc8689a…ee79
6 touches
3 conflicts
0xc9666555…14b8
0x34b655…2a6f
6 touches
3 conflicts
0xd0f6f4f2…dffa
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdc69def1…fa0b
0x34b655…2a6f
6 touches
3 conflicts
0xfe59123f…073a
0x34b655…2a6f
6 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
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
6 conflicts on slot 0xc36881859a…c49b36
Audit this contract →
← previous block·next block →recent activity