← previous blocknext block →recent activity
Analyzing
Block #99,709,019
13 transactions · 13 stateful · 2026-08-27 20:30:29 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,709,019 · 13 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
4w07w08w09w110w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36f91801…9b29
0x8964d7…10f8
4 touches
1 conflict
0x36f91801…9b2a
0x8964d7…10f8
4 touches
1 conflict
0x36f91801…9b2d
0x8964d7…10f8
4 touches
1 conflict
0x36f91801…9b2e
0x8964d7…10f8
4 touches
1 conflict
0x36f91801…9b30
0x8964d7…10f8
4 touches
1 conflict
0x08399ab6…0057
0x34b655…2a6f
4 touches
1 conflict
0x793357cd…1653
0x34b655…2a6f
4 touches
1 conflict
0xad79410b…96a5
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: 0x8964d7c9…5b10f8
1 conflict on slot 0x36f9180165…259b29
Audit this contract →
← previous block·next block →recent activity