← previous blocknext block →recent activity
Analyzing
Block #98,768,569
26 transactions · 26 stateful · 2026-08-24 13:22:05 UTC
Parallelism
85/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,768,569 · 26 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
1w02w13w05w06w17w110w011w112w013w115w217w021w023w124w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3981be5…2c47
0x34b655…2a6f
6 touches
3 conflicts
0x20b50479…b75c
0x0158ab…1a70
4 touches
1 conflict
0x81b59a11…e211
0x0158ab…1a70
4 touches
1 conflict
0x00000000…0000
0x0c428e…07a4
4 touches
1 conflict
0x00000000…0002
0x0c428e…07a4
4 touches
1 conflict
0x00000000…0003
0x0c428e…07a4
4 touches
1 conflict
0x22badbc6…4c24
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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 0xf3981be56e…f02c47
Audit this contract →
← previous block·next block →recent activity