← previous blocknext block →recent activity
Analyzing
Block #98,261,628
29 transactions · 28 stateful · 2026-08-22 18:15:16 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.66
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,261,628 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w19w011w012w117w019w020w121w123w124w225w326w427w528w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0x7aad02c6…b979
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
8 touches
6 conflicts
0xb20094ed…0fef
0x34b655…2a6f
6 touches
3 conflicts
0x77cf3c7b…a722
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0x00000000…0007
0x340143…768f
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
10 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity