← previous blocknext block →recent activity
Analyzing
Block #87,710,628
17 transactions · 17 stateful · 2026-07-14 13:40:14 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,710,628 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w18w19w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x0ba865dd…a249
0x34b655…2a6f
4 touches
1 conflict
0x3e950538…2259
0x34b655…2a6f
4 touches
1 conflict
0x4f1e16d4…4833
0x34b655…2a6f
4 touches
1 conflict
0x5e5ce24b…6023
0x34b655…2a6f
4 touches
1 conflict
0x6c2aa5be…d808
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity