← previous blocknext block →recent activity
Analyzing
Block #87,641,940
33 transactions · 24 stateful · 2026-07-14 06:00:53 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,641,940 · 33 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w09w110w215w216w318w020w121w124w228w029w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x948e8d20…a8df
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x83058c4e…c7cc
0x34b655…2a6f
6 touches
3 conflicts
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92aaa948…2b73
0x34b655…2a6f
4 touches
1 conflict
0x9aa29e0c…eb5b
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
6 conflicts on slot 0x948e8d208e…02a8df
Audit this contract →
← previous block·next block →recent activity