← previous blocknext block →recent activity
Analyzing
Block #98,671,490
24 transactions · 20 stateful · 2026-08-24 05:09:02 UTC
Parallelism
88/100
Blocked
45%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,671,490 · 24 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
1w02w13w16w07w18w09w010w116w117w218w219w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd97b0449…00a0
0x34b655…2a6f
6 touches
3 conflicts
0x8947e2e8…cdb3
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x074c08f8…fb56
0x34b655…2a6f
4 touches
1 conflict
0x27b6010e…e4aa
0x34b655…2a6f
4 touches
1 conflict
0x3f798539…99c4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xd97b04496e…0c00a0
Audit this contract →
← previous block·next block →recent activity