← previous blocknext block →recent activity
Analyzing
Block #98,754,321
25 transactions · 18 stateful · 2026-08-24 12:10:21 UTC
Parallelism
84/100
Blocked
44%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,754,321 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w010w111w012w013w115w217w218w119w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31f08c56…70a5
0x40c49f…2af0
6 touches
3 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xb64473b0…0d6f
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6e3e9f18…f684
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x065ff70b…356d
0x40c49f…2af0
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: 0x40c49f17…d22af0
3 conflicts on slot 0x31f08c5652…9370a5
Audit this contract →
← previous block·next block →recent activity