← previous blocknext block →recent activity
Analyzing
Block #86,807,588
19 transactions · 18 stateful · 2026-07-10 09:01:21 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,807,588 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w27w38w09w112w116w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa37e64f8…ba05
0x34b655…2a6f
8 touches
6 conflicts
0x5b9e5ecc…2bc7
0x34b655…2a6f
6 touches
3 conflicts
0xec7fe04a…3c56
0x34b655…2a6f
6 touches
3 conflicts
0x698e3c53…a4c4
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x823a3658…acf6
0x34b655…2a6f
4 touches
1 conflict
0x85ec9605…9fdd
0x34b655…2a6f
4 touches
1 conflict
0x890eac6e…1c0d
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
6 conflicts on slot 0xa37e64f8b9…21ba05
Audit this contract →
← previous block·next block →recent activity