← previous blocknext block →recent activity
Analyzing
Block #86,628,285
14 transactions · 13 stateful · 2026-07-09 13:02:37 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,628,285 · 14 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
1w02w14w05w16w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4caf91f9…8ab5
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1a9
0xb1dbf0…c0d3
4 touches
1 conflict
0x00000000…0004
0xb1dbf0…c0d3
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
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 0x4caf91f97b…528ab5
Audit this contract →
← previous block·next block →recent activity