← previous blocknext block →recent activity
Analyzing
Block #87,503,888
52 transactions · 34 stateful · 2026-07-13 14:36:54 UTC
Parallelism
65/100
Blocked
62%
Avg conflicts / tx
1.87
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,503,888 · 52 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w09w010w113w014w126w227w328w429w530w631w732w833w934w1036w1237w1339w1445w1646w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
14 touches
21 conflicts
0x18e37e7d…bab2
0x34b655…2a6f
10 touches
10 conflicts
0x2a9f9737…d07d
0x34b655…2a6f
10 touches
10 conflicts
0x44b77b2c…dff3
0x34b655…2a6f
10 touches
10 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
10 touches
10 conflicts
0x57635821…c27b
0x34b655…2a6f
10 touches
10 conflicts
0x6b2ba712…0214
0x34b655…2a6f
10 touches
10 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