← previous blocknext block →recent activity
Analyzing
Block #99,196,689
15 transactions · 14 stateful · 2026-08-26 01:22:55 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,196,689 · 15 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
2w04w05w17w08w09w111w112w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61c5a0d4…5107
0x8964d7…10f8
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x61c5a0d4…5100
0x8964d7…10f8
6 touches
3 conflicts
0x61c5a0d4…5101
0x8964d7…10f8
6 touches
3 conflicts
0x61c5a0d4…5104
0x8964d7…10f8
6 touches
3 conflicts
0x61c5a0d4…5105
0x8964d7…10f8
6 touches
3 conflicts
0xac2a0273…721b
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 0x61c5a0d4f5…e05107
Audit this contract →
← previous block·next block →recent activity