← previous blocknext block →recent activity
Analyzing
Block #99,253,972
21 transactions · 15 stateful · 2026-08-26 06:11:08 UTC
Parallelism
90/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,253,972 · 21 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w114w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48203298…65cb
0x34b655…2a6f
4 touches
1 conflict
0xf7e4bb12…b40a
0x34b655…2a6f
4 touches
1 conflict
0xb5c7c6aa…fdba
0x34b655…2a6f
4 touches
1 conflict
0x4984f7be…d515
0x34b655…2a6f
4 touches
1 conflict
0xfa443a44…72a4
0xd32edf…ff58
3 touches
1 conflict
0x6d0d6733…67ce
0x065c9d…c394
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a568
0x188d58…ea8e
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
1 conflict on slot 0x4820329863…2a65cb
Audit this contract →
← previous block·next block →recent activity