← previous blocknext block →recent activity
Analyzing
Block #87,285,599
13 transactions · 11 stateful · 2026-07-12 14:17:07 UTC
Parallelism
54/100
Blocked
55%
Avg conflicts / tx
1.31
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,285,599 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w37w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x016f88ec…46fc
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
6 touches
3 conflicts
0x00cd9338…40d2
0x34b655…2a6f
6 touches
3 conflicts
0x66f7b1ee…a38b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x818b0b44…ff6f
0x34b655…2a6f
4 touches
1 conflict
0x8b501dcf…1040
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
10 conflicts on slot 0x016f88ec76…8446fc
Audit this contract →
← previous block·next block →recent activity