← previous blocknext block →recent activity
Analyzing
Block #98,914,163
25 transactions · 17 stateful · 2026-08-25 01:34:46 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,914,163 · 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
1w05w17w213w015w016w018w121w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x65ff54af…aa01
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641d
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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity