← previous blocknext block →recent activity
Analyzing
Block #99,090,009
17 transactions · 16 stateful · 2026-08-25 16:26:03 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,090,009 · 17 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
2w03w04w15w06w17w08w110w111w012w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x7711cbff…294e
0x8964d7…10f8
6 touches
3 conflicts
0x7711cbff…294f
0x8964d7…10f8
6 touches
3 conflicts
0x7711cbff…2952
0x8964d7…10f8
6 touches
3 conflicts
0x7711cbff…2953
0x8964d7…10f8
6 touches
3 conflicts
0x7711cbff…2955
0x8964d7…10f8
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0xd1b40f29…9b9d
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
3 conflicts on slot 0x0000000000…000008
Audit this contract →
← previous block·next block →recent activity