← previous blocknext block →recent activity
Analyzing
Block #87,363,016
24 transactions · 22 stateful · 2026-07-12 22:54:45 UTC
Parallelism
79/100
Blocked
55%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,363,016 · 24 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
1w03w04w15w26w17w210w011w113w214w315w316w217w420w423w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
8 touches
6 conflicts
0xc4e19ae4…0788
0xe7cd86…c82d
6 touches
3 conflicts
0x31ec17e3…8912
0x34b655…2a6f
6 touches
3 conflicts
0x31ec17e3…8913
0x34b655…2a6f
6 touches
3 conflicts
0xddbb53a9…9198
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0090639e…243e
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity