← previous blocknext block →recent activity
Analyzing
Block #87,346,371
16 transactions · 15 stateful · 2026-07-12 21:03:28 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,346,371 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w39w110w411w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa09be165…16b9
0x34b655…2a6f
12 touches
15 conflicts
0x8d59b150…7225
0x34b655…2a6f
8 touches
6 conflicts
0x8eedf936…a0c3
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xa112f315…1a92
0x34b655…2a6f
8 touches
6 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xef0c75c6…b3de
0x34b655…2a6f
6 touches
3 conflicts
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
15 conflicts on slot 0xa09be1653e…8116b9
Audit this contract →
← previous block·next block →recent activity