← previous blocknext block →recent activity
Analyzing
Block #87,753,972
13 transactions · 12 stateful · 2026-07-14 18:30:20 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,753,972 · 13 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
1w02w14w05w18w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64800813…db9f
0x34b655…2a6f
6 touches
3 conflicts
0x3e8b3a49…53ee
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x016f88ec…46fc
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x19caa5cc…17c7
0x34b655…2a6f
4 touches
1 conflict
0x441ddfe3…535b
0x34b655…2a6f
4 touches
1 conflict
0x64929e6e…cf16
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
3 conflicts on slot 0x64800813fa…1bdb9f
Audit this contract →
← previous block·next block →recent activity