← previous blocknext block →recent activity
Analyzing
Block #99,036,622
14 transactions · 14 stateful · 2026-08-25 11:53:51 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,036,622 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w08w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68dfc6ca…56ac
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xdbc423ba…59fc
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x3bdce863…b4e0
0x34b655…2a6f
2 touches
0 conflicts
0x40792dd3…a7fd
0x34b655…2a6f
2 touches
0 conflicts
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 0x68dfc6ca63…a056ac
Audit this contract →
← previous block·next block →recent activity