← previous blocknext block →recent activity
Analyzing
Block #87,723,147
36 transactions · 28 stateful · 2026-07-14 15:04:07 UTC
Parallelism
61/100
Blocked
68%
Avg conflicts / tx
2.64
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,723,147 · 36 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w09w110w213w014w115w216w317w418w519w620w721w822w923w1026w227w828w932w733w1134w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x3d158563…8713
0x34b655…2a6f
10 touches
10 conflicts
0x0dd44476…ef40
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xa55aabd7…cdfd
0x34b655…2a6f
8 touches
6 conflicts
0xbfb7adca…51d7
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe6e6f436…ddc0
0x34b655…2a6f
8 touches
6 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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity