← previous blocknext block →recent activity
Analyzing
Block #87,730,191
20 transactions · 19 stateful · 2026-07-14 15:51:15 UTC
Parallelism
60/100
Blocked
68%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,730,191 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w717w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ec64628…72e4
0x34b655…2a6f
16 touches
28 conflicts
0x0ba865dd…a249
0x34b655…2a6f
14 touches
21 conflicts
0x5170a218…3a84
0xc8689a…ee79
14 touches
21 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
14 touches
21 conflicts
0xbf768a2f…f453
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
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
28 conflicts on slot 0x5ec6462858…6272e4
Audit this contract →
← previous block·next block →recent activity