← previous blocknext block →recent activity
Analyzing
Block #98,524,650
17 transactions · 17 stateful · 2026-08-23 16:23:54 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,524,650 · 17 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
1w03w05w06w18w29w311w113w415w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x279ddfdc…78fb
0x34b655…2a6f
4 touches
1 conflict
0x279ddfdc…78fc
0x34b655…2a6f
4 touches
1 conflict
0x44c9cb1f…59b3
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
6 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity