← previous blocknext block →recent activity
Analyzing
Block #87,319,359
22 transactions · 19 stateful · 2026-07-12 18:02:50 UTC
Parallelism
91/100
Blocked
11%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,319,359 · 22 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
1w02w17w08w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7b28ab0…40d1
0x34b655…2a6f
4 touches
1 conflict
0xd2171a4a…a036
0x34b655…2a6f
4 touches
1 conflict
0xcfb9b777…5e1b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc815e4a5…ca3c
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x226e3b61…5e6f
0x34b655…2a6f
4 touches
1 conflict
0x31519d10…f76b
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
1 conflict on slot 0xb7b28ab0c6…fd40d1
Audit this contract →
← previous block·next block →recent activity