← previous blocknext block →recent activity
Analyzing
Block #87,638,616
12 transactions · 7 stateful · 2026-07-14 05:38:44 UTC
Parallelism
83/100
Blocked
14%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,638,616 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0933feb3…9664
0x34b655…2a6f
4 touches
1 conflict
0x7451f320…a9f6
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a4
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xbf6de35e…bafd
0x34b655…2a6f
4 touches
1 conflict
0xda6ebfcf…d51e
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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 0x0933feb33c…ec9664
Audit this contract →
← previous block·next block →recent activity