← previous blocknext block →recent activity
Analyzing
Block #87,737,639
30 transactions · 25 stateful · 2026-07-14 16:41:05 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,737,639 · 30 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
5w06w17w28w09w112w013w114w219w220w023w324w427w128w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
10 touches
10 conflicts
0x1bc07c63…d6ad
0x34b655…2a6f
6 touches
3 conflicts
0x0363d65e…06d2
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xbc94dfe1…0b3d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0001
0xc1ff9f…b0fc
6 touches
3 conflicts
0x680ca7d7…2df4
0x34b655…2a6f
4 touches
1 conflict
0x76ebf9c2…e0ef
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 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity