← previous blocknext block →recent activity
Analyzing
Block #87,624,647
19 transactions · 17 stateful · 2026-07-14 04:05:17 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,624,647 · 19 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
1w02w16w07w18w210w011w113w214w315w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7afbac8f…9cad
0x34b655…2a6f
8 touches
6 conflicts
0x493e876e…c60c
0x01bff4…1071
6 touches
3 conflicts
0x6927695a…d15b
0x01bff4…1071
6 touches
3 conflicts
0xf7640726…19a2
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x263aa68b…6c6a
0x34b655…2a6f
6 touches
3 conflicts
0xcc43c7de…9641
0x851145…3f07
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 0x7afbac8f45…fb9cad
Audit this contract →
← previous block·next block →recent activity