← previous blocknext block →recent activity
Analyzing
Block #87,582,653
16 transactions · 14 stateful · 2026-07-13 23:24:29 UTC
Parallelism
81/100
Blocked
14%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,582,653 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d2f0b01…112a
0x34b655…2a6f
4 touches
1 conflict
0xfd77e6c1…264b
0x34b655…2a6f
4 touches
1 conflict
0xa9cf4e1b…9bf4
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x8299fe6c…5752
0x34b655…2a6f
2 touches
0 conflicts
0xc09c3422…3c8b
0x34b655…2a6f
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 0x5d2f0b01fb…19112a
Audit this contract →
← previous block·next block →recent activity