← previous blocknext block →recent activity
Analyzing
Block #87,418,101
15 transactions · 13 stateful · 2026-07-13 05:03:16 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,418,101 · 15 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
1w02w03w14w25w09w110w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0xa457c06e…2f06
0x34b655…2a6f
4 touches
1 conflict
0xaa99c369…263d
0x34b655…2a6f
4 touches
1 conflict
0xab774675…75f7
0x34b655…2a6f
4 touches
1 conflict
0xb13b96bd…a3cb
0x34b655…2a6f
4 touches
1 conflict
0xb7e4c78a…f3f6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x922c7ebd…6600
0xc8689a…ee79
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
3 conflicts on slot 0x8e5cc69035…0db06b
Audit this contract →
← previous block·next block →recent activity