← previous blocknext block →recent activity
Analyzing
Block #87,612,611
50 transactions · 33 stateful · 2026-07-14 02:44:48 UTC
Parallelism
70/100
Blocked
73%
Avg conflicts / tx
1.9
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,612,611 · 50 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w08w19w210w311w012w125w026w227w328w429w530w631w732w833w934w1041w143w144w248w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
16 touches
28 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
12 touches
15 conflicts
0xed59b1cd…8509
0x34b655…2a6f
12 touches
15 conflicts
0x201679bc…0414
0x34b655…2a6f
12 touches
15 conflicts
0x49f75237…44f4
0x34b655…2a6f
12 touches
15 conflicts
0x67905f6e…02a1
0x34b655…2a6f
12 touches
15 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
12 touches
15 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