← previous blocknext block →recent activity
Analyzing
Block #99,253,425
15 transactions · 13 stateful · 2026-08-26 06:08:22 UTC
Parallelism
80/100
Blocked
23%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,253,425 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w010w111w113w014w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7f59f1b…fb6c
0x34b655…2a6f
6 touches
3 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x9427ba7e…fcf9
0x8964d7…10f8
4 touches
1 conflict
0x0203a60f…d0bd
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
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 0xe7f59f1b8a…72fb6c
Audit this contract →
← previous block·next block →recent activity