← previous blocknext block →recent activity
Analyzing
Block #87,489,416
19 transactions · 18 stateful · 2026-07-13 13:00:04 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,489,416 · 19 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
1w03w14w07w08w19w210w311w012w113w214w315w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88adad52…54b7
0x34b655…2a6f
8 touches
6 conflicts
0xf79df061…e005
0xe52b14…7230
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x96bfa04d…d06b
0x34b655…2a6f
4 touches
1 conflict
0xb88e5f26…1ca6
0x34b655…2a6f
4 touches
1 conflict
0x9a85f019…ae58
0x065c9d…c394
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
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 0x88adad5202…7d54b7
Audit this contract →
← previous block·next block →recent activity