← previous blocknext block →recent activity
Analyzing
Block #87,489,379
16 transactions · 16 stateful · 2026-07-13 12:59:49 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.69
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,489,379 · 16 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
2w03w15w26w39w010w411w512w614w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x3a5224d1…ee57
0x34b655…2a6f
10 touches
10 conflicts
0xe4af56d6…5a50
0x34b655…2a6f
10 touches
10 conflicts
0x57c8db9d…3979
0x34b655…2a6f
10 touches
10 conflicts
0xe677be37…eaf2
0x34b655…2a6f
8 touches
6 conflicts
0xec3f89f7…5b93
0x34b655…2a6f
6 touches
3 conflicts
0x18dd8844…6133
0x34b655…2a6f
6 touches
3 conflicts
0x683dbabb…acd8
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity