← previous blocknext block →recent activity
Analyzing
Block #87,712,770
14 transactions · 14 stateful · 2026-07-14 13:54:34 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,712,770 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w07w18w29w110w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x1ec7ada6…505b
0x34b655…2a6f
8 touches
6 conflicts
0xf4a27876…b09c
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
8 touches
6 conflicts
0x52e57273…fe8f
0x34b655…2a6f
8 touches
6 conflicts
0x77da9367…274d
0x34b655…2a6f
7 touches
6 conflicts
0x051237de…2cca
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity