← previous blocknext block →recent activity
Analyzing
Block #87,417,432
18 transactions · 16 stateful · 2026-07-13 04:58:48 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,417,432 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w18w09w110w213w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x83539b28…24e0
0x34b655…2a6f
6 touches
3 conflicts
0xfb647416…9969
0x34b655…2a6f
6 touches
3 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
6 touches
3 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
6 touches
3 conflicts
0xca2926e0…61b5
0x34b655…2a6f
6 touches
3 conflicts
0x4118bd12…924a
0x34b655…2a6f
4 touches
1 conflict
0x5ad8135f…d8e6
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
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
3 conflicts on slot 0x83539b28a9…d924e0
Audit this contract →
← previous block·next block →recent activity