← previous blocknext block →recent activity
Analyzing
Block #98,665,991
52 transactions · 45 stateful · 2026-08-24 04:40:25 UTC
Parallelism
75/100
Blocked
64%
Avg conflicts / tx
1.85
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #98,665,991 · 52 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w19w010w111w012w115w016w117w219w021w222w323w425w527w229w234w335w136w239w543w447w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x2a9e9bd1…5368
0x2a68ba…90c5
10 touches
10 conflicts
0xd7929998…3ae8
0xa6afd3…d132
9 touches
10 conflicts
0x11b69a7e…334e
0xee8c0e…1242
8 touches
6 conflicts
0x30908823…a62d
0x34b655…2a6f
8 touches
6 conflicts
0xf98db8ee…a56d
0x34b655…2a6f
8 touches
6 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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity