← previous blocknext block →recent activity
Analyzing
Block #87,417,566
19 transactions · 18 stateful · 2026-07-13 04:59:42 UTC
Parallelism
63/100
Blocked
39%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,417,566 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w17w28w311w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x563bbb55…861a
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xb16c57be…181e
0x34b655…2a6f
6 touches
3 conflicts
0xc3c7cf34…43da
0x34b655…2a6f
6 touches
3 conflicts
0xea4b86ec…900f
0x34b655…2a6f
6 touches
3 conflicts
0x0ba6faa0…a9cf
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 0x563bbb557a…02861a
Audit this contract →
← previous block·next block →recent activity