← previous blocknext block →recent activity
Analyzing
Block #87,350,423
25 transactions · 23 stateful · 2026-07-12 21:30:33 UTC
Parallelism
56/100
Blocked
57%
Avg conflicts / tx
2.44
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,350,423 · 25 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w17w08w19w210w311w412w513w614w715w816w920w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
22 touches
55 conflicts
0x75a25a1c…d367
0x34b655…2a6f
18 touches
36 conflicts
0x17fbe072…2ea6
0x34b655…2a6f
16 touches
28 conflicts
0x2807ae1a…73b6
0x34b655…2a6f
16 touches
28 conflicts
0x40dcade7…495d
0x34b655…2a6f
16 touches
28 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
16 touches
28 conflicts
0x0dd44476…ef40
0x34b655…2a6f
16 touches
28 conflicts
0x564d127d…5e3f
0x34b655…2a6f
16 touches
28 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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity