← previous blocknext block →recent activity
Analyzing
Block #87,498,302
24 transactions · 19 stateful · 2026-07-13 13:59:31 UTC
Parallelism
83/100
Blocked
26%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,498,302 · 24 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
2w03w14w013w014w115w216w018w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
8 touches
6 conflicts
0x00cd9338…40d2
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x1f6de02e…874b
0x34b655…2a6f
4 touches
1 conflict
0x369883e3…a449
0x34b655…2a6f
4 touches
1 conflict
0x50ca370b…22ad
0x34b655…2a6f
4 touches
1 conflict
0x84e7c382…48ae
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity