← previous blocknext block →recent activity
Analyzing
Block #87,918,270
54 transactions · 37 stateful · 2026-07-15 12:49:17 UTC
Parallelism
69/100
Blocked
70%
Avg conflicts / tx
1.7
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,918,270 · 54 txs across 17 waves · depth 17
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
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w210w011w116w017w119w020w129w230w335w736w837w938w239w1040w342w443w344w545w648w1149w1251w1453w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x58126412…4dad
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
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
21 conflicts on slot 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity