← previous blocknext block →recent activity
Analyzing
Block #99,209,417
15 transactions · 12 stateful · 2026-08-26 02:26:57 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,209,417 · 15 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
1w02w06w17w110w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd08db6ee…a943
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x1b5ebb84…9788
0x40c49f…2af0
4 touches
1 conflict
0x5f8443aa…f7dc
0x40c49f…2af0
4 touches
1 conflict
0x1c831236…a132
0x34b655…2a6f
4 touches
1 conflict
0x3f798539…99c4
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x5d3edf37…6e51
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: 0x40c49f17…d22af0
1 conflict on slot 0xd08db6eea8…34a943
Audit this contract →
← previous block·next block →recent activity