← previous blocknext block →recent activity
Analyzing
Block #87,317,562
17 transactions · 17 stateful · 2026-07-12 17:50:50 UTC
Parallelism
88/100
Blocked
12%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,317,562 · 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
1w04w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x1c8b4f85…d07d
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x442dc980…b7ca
0x34b655…2a6f
2 touches
0 conflicts
0x66f7b1ee…a38b
0x34b655…2a6f
2 touches
0 conflicts
0x9a287655…f785
0x34b655…2a6f
2 touches
0 conflicts
0xab1fd3cc…5bf7
0x34b655…2a6f
2 touches
0 conflicts
0xd1c5aeea…ee0a
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity