← previous blocknext block →recent activity
Analyzing
Block #98,083,954
15 transactions · 14 stateful · 2026-08-22 03:20:39 UTC
Parallelism
47/100
Blocked
57%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,083,954 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xb1277a25…706f
0x34b655…2a6f
6 touches
3 conflicts
0x9899b46b…e84d
0x34b655…2a6f
5 touches
3 conflicts
0x8311570f…5321
0x34b655…2a6f
4 touches
1 conflict
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xfaf89f45…ced6
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity