← previous blocknext block →recent activity
Analyzing
Block #98,851,010
18 transactions · 16 stateful · 2026-08-24 20:17:04 UTC
Parallelism
61/100
Blocked
38%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,851,010 · 18 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
5w06w17w28w39w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
8 touches
6 conflicts
0x7fd79ea3…482b
0x851145…3f07
7 touches
6 conflicts
0xa06e4d31…98e3
0x851145…3f07
7 touches
6 conflicts
0xf13704e6…258a
0x01bff4…1071
4 touches
1 conflict
0x595233b5…c4aa
0x754704…b603
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: 0x01bff417…bc1071
15 conflicts on slot 0x11b69a7ea1…83334e
Audit this contract →
← previous block·next block →recent activity