← previous blocknext block →recent activity
Analyzing
Block #87,332,993
16 transactions · 16 stateful · 2026-07-12 19:34:03 UTC
Parallelism
88/100
Blocked
6%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,332,993 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4c38fb0…ebf5
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a3
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a4
0x34b655…2a6f
4 touches
1 conflict
0x4b0551c8…6502
0x34b655…2a6f
4 touches
1 conflict
0x6dd7e78d…7a4b
0x34b655…2a6f
4 touches
1 conflict
0x7fb5d16a…c374
0x34b655…2a6f
3 touches
1 conflict
0xf6f2cfd8…fd0f
0x065c9d…c394
2 touches
0 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
1 conflict on slot 0xd4c38fb012…33ebf5
Audit this contract →
← previous block·next block →recent activity