← previous blocknext block →recent activity
Analyzing
Block #98,088,524
23 transactions · 19 stateful · 2026-08-22 03:43:39 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,088,524 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w07w18w29w210w311w112w417w018w521w622w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ee8b564…4c49
0x34b655…2a6f
10 touches
10 conflicts
0xc0e4fec9…aec9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xd25997d0…a687
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0x3ee8b5644d…f04c49
Audit this contract →
← previous block·next block →recent activity