← previous blocknext block →recent activity
Analyzing
Block #87,168,995
23 transactions · 19 stateful · 2026-07-12 01:16:31 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,168,995 · 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
2w05w16w28w09w111w012w113w214w315w417w018w119w221w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76ee219a…508f
0x34b655…2a6f
10 touches
10 conflicts
0x4e3abeff…18eb
0x34b655…2a6f
10 touches
10 conflicts
0x74a7b40b…8922
0x34b655…2a6f
10 touches
10 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
10 touches
10 conflicts
0x00e21a9f…3583
0x34b655…2a6f
10 touches
10 conflicts
0xe5e62b65…be7c
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x2484cc15…5afc
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x76ee219a30…04508f
Audit this contract →
← previous block·next block →recent activity