← previous blocknext block →recent activity
Analyzing
Block #99,117,269
17 transactions · 15 stateful · 2026-08-25 18:43:17 UTC
Parallelism
59/100
Blocked
67%
Avg conflicts / tx
1.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,117,269 · 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
1w02w13w06w18w29w210w311w113w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x326a02b5…8dad
0x34b655…2a6f
12 touches
15 conflicts
0x62910921…3016
0x34b655…2a6f
12 touches
15 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
6 touches
3 conflicts
0x57be321f…fecc
0x34b655…2a6f
5 touches
3 conflicts
0x04795529…c98b
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: Perpl
21 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity