← previous blocknext block →recent activity
Analyzing
Block #87,639,913
18 transactions · 15 stateful · 2026-07-14 05:47:23 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,639,913 · 18 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
1w03w07w08w19w110w111w012w213w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf386bff1…b350
0x34b655…2a6f
6 touches
3 conflicts
0x288f34c1…4602
0x0a2fbf…29b1
4 touches
1 conflict
0x288f34c1…4603
0x0a2fbf…29b1
4 touches
1 conflict
0x288f34c1…4606
0x0a2fbf…29b1
4 touches
1 conflict
0x85b9b212…905d
0x0a2fbf…29b1
4 touches
1 conflict
0x85b9b212…905e
0x0a2fbf…29b1
4 touches
1 conflict
0x0b05d77e…6f90
0x34b655…2a6f
4 touches
1 conflict
0x10ae525c…1c0f
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
3 conflicts on slot 0xf386bff13e…f6b350
Audit this contract →
← previous block·next block →recent activity