← previous blocknext block →recent activity
Analyzing
Block #98,023,405
25 transactions · 23 stateful · 2026-08-21 22:15:56 UTC
Parallelism
80/100
Blocked
52%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,023,405 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w07w08w19w210w311w415w018w220w121w223w324w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
10 touches
10 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdfda089f…747f
0x3bd359…433a
6 touches
3 conflicts
0xd6b1b633…6723
0x754704…b603
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x5a3732cb…edaf
0x1b6862…e19c
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: 0xbb3f3cb7…74e046
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity