← previous blocknext block →recent activity
Analyzing
Block #87,301,730
16 transactions · 15 stateful · 2026-07-12 16:04:57 UTC
Parallelism
56/100
Blocked
60%
Avg conflicts / tx
1.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,301,730 · 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
2w03w16w17w28w39w410w511w612w315w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033dddd2…ac15
0x34b655…2a6f
14 touches
21 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x0f6666e6…f280
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x823a3658…acf6
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
21 conflicts on slot 0x033dddd296…07ac15
Audit this contract →
← previous block·next block →recent activity