← previous blocknext block →recent activity
Analyzing
Block #87,419,021
17 transactions · 13 stateful · 2026-07-13 05:09:24 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,419,021 · 17 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
6w07w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x574a8378…b246
0x34b655…2a6f
4 touches
1 conflict
0x36a846dc…cf4d
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x0bcd5982…f1f8
0x34b655…2a6f
2 touches
0 conflicts
0x12447785…398c
0x34b655…2a6f
2 touches
0 conflicts
0x169daa40…3f75
0x34b655…2a6f
2 touches
0 conflicts
0x1a04fff3…c30a
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 0x5e782d178d…db5318
Audit this contract →
← previous block·next block →recent activity