← previous blocknext block →recent activity
Analyzing
Block #99,164,105
23 transactions · 23 stateful · 2026-08-25 22:38:59 UTC
Parallelism
87/100
Blocked
13%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,164,105 · 23 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
2w03w04w15w06w214w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38aa1898…fdf5
0x3bd359…433a
6 touches
3 conflicts
0xd06cc746…27e4
0x5ef52d…4343
6 touches
3 conflicts
0xa5a4bb2c…f2c7
0x188d58…ea8e
6 touches
3 conflicts
0xaecd6ed8…95ad
0x188d58…ea8e
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x33450b54…6744
0x188d58…ea8e
4 touches
1 conflict
0xd6dfef8e…4721
0x0eb88f…c0cc
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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: Wrapped MON (WMON)
3 conflicts on slot 0x38aa189812…48fdf5
Audit this contract →
← previous block·next block →recent activity