← previous blocknext block →recent activity
Analyzing
Block #99,270,216
17 transactions · 15 stateful · 2026-08-26 07:32:56 UTC
Parallelism
59/100
Blocked
47%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,270,216 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w09w010w111w112w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x886db264…846e
0x34b655…2a6f
12 touches
15 conflicts
0xff38b4dd…8268
0x34b655…2a6f
8 touches
6 conflicts
0xbc55e125…a9ab
0x34b655…2a6f
6 touches
3 conflicts
0x8b2b7213…4899
0x34b655…2a6f
6 touches
3 conflicts
0x557908f3…a476
0x34b655…2a6f
5 touches
3 conflicts
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
21 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity