← previous blocknext block →recent activity
Analyzing
Block #87,621,157
19 transactions · 15 stateful · 2026-07-14 03:41:56 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
0.53
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,621,157 · 19 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
3w04w17w28w39w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf827da3…f2a5
0x34b655…2a6f
8 touches
6 conflicts
0xd22ea5b1…7dcb
0x34b655…2a6f
4 touches
1 conflict
0xd517f20d…2c0f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf346808d…6ad4
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0xd026fe03…7748
0x34b655…2a6f
4 touches
1 conflict
0x69ce640b…884a
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 0xcf827da350…31f2a5
Audit this contract →
← previous block·next block →recent activity