← previous blocknext block →recent activity
Analyzing
Block #99,210,194
36 transactions · 29 stateful · 2026-08-26 02:30:51 UTC
Parallelism
69/100
Blocked
52%
Avg conflicts / tx
1.5
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #99,210,194 · 36 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w08w19w012w115w016w018w121w122w023w124w025w228w330w532w733w834w935w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0x737acb78…fce8
0x34b655…2a6f
14 touches
21 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
10 touches
10 conflicts
0x4b0529ae…4e89
0x34b655…2a6f
8 touches
6 conflicts
0x41a8cbc7…0ff1
0x34b655…2a6f
5 touches
3 conflicts
0x0f4d9f2d…ac65
0x34b655…2a6f
5 touches
3 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity