← previous blocknext block →recent activity
Analyzing
Block #87,786,232
13 transactions · 12 stateful · 2026-07-14 22:06:10 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,786,232 · 13 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
2w04w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ed58b36…c5e5
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x55c2c22c…0474
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0xb96a99db…95aa
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xc6b9bb4b…145a
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
1 conflict on slot 0x5ed58b3680…35c5e5
Audit this contract →
← previous block·next block →recent activity