← previous blocknext block →recent activity
Analyzing
Block #87,750,170
22 transactions · 21 stateful · 2026-07-14 18:04:55 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
1.45
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,750,170 · 22 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
1w02w16w17w28w39w411w012w113w215w317w418w520w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ab016af…dae9
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
10 touches
10 conflicts
0x0dd44476…ef40
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x3fde350e…8d43
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x03d5b686…1c00
0x34b655…2a6f
8 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
15 conflicts on slot 0x7ab016afb2…a7dae9
Audit this contract →
← previous block·next block →recent activity