← previous blocknext block →recent activity
Analyzing
Block #99,207,345
14 transactions · 13 stateful · 2026-08-26 02:16:31 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,207,345 · 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
2w06w07w18w29w110w311w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac163e96…53ee
0x34b655…2a6f
8 touches
6 conflicts
0xe3684e08…c96a
0x34b655…2a6f
6 touches
3 conflicts
0x4f458401…2b41
0x851145…3f07
4 touches
1 conflict
0xa52ff19e…48b2
0x851145…3f07
4 touches
1 conflict
0xa6b936e6…22eb
0x851145…3f07
4 touches
1 conflict
0x38bcfe5f…6c71
0x34b655…2a6f
4 touches
1 conflict
0x4188cc5f…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x8d5fc820…1750
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
6 conflicts on slot 0xac163e969a…fc53ee
Audit this contract →
← previous block·next block →recent activity