← previous blocknext block →recent activity
Analyzing
Block #87,704,483
32 transactions · 20 stateful · 2026-07-14 12:59:05 UTC
Parallelism
88/100
Blocked
45%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,704,483 · 32 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w16w27w08w121w022w123w225w326w327w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xdb529f62…663c
0x34b655…2a6f
8 touches
6 conflicts
0xa524a39b…df24
0x34b655…2a6f
8 touches
6 conflicts
0x88413c1a…7783
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
8 touches
6 conflicts
0x56f6adae…573c
0x34b655…2a6f
8 touches
6 conflicts
0xe29ab678…8d26
0x34b655…2a6f
7 touches
6 conflicts
0x9825f5b0…97a9
0x34b655…2a6f
7 touches
6 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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity