← previous blocknext block →recent activity
Analyzing
Block #98,421,111
17 transactions · 16 stateful · 2026-08-23 07:37:40 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,421,111 · 17 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
1w02w14w05w08w212w013w114w115w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9660902a…a12b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x3e598447…0e3f
0xa6afd3…d132
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c2
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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 0x9660902a7f…cba12b
Audit this contract →
← previous block·next block →recent activity