← previous blocknext block →recent activity
Analyzing
Block #99,109,800
29 transactions · 25 stateful · 2026-08-25 18:05:41 UTC
Parallelism
90/100
Blocked
28%
Avg conflicts / tx
0.34
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,109,800 · 29 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
5w06w17w08w115w016w117w219w020w126w027w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4888af6…26b5
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x9c168b41…7486
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xaf498679…7732
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
3 conflicts on slot 0xc4888af66a…2f26b5
Audit this contract →
← previous block·next block →recent activity