← previous blocknext block →recent activity
Analyzing
Block #99,170,761
12 transactions · 12 stateful · 2026-08-25 23:12:28 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,170,761 · 12 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
4w05w06w17w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0xf92e07d1…0c1e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd4305f3b…7f3e
0x34b655…2a6f
4 touches
1 conflict
0x461661b9…f714
0x34b655…2a6f
2 touches
0 conflicts
0x4cc25406…1c0d
0x34b655…2a6f
2 touches
0 conflicts
0x52404f3d…4c2e
0x34b655…2a6f
2 touches
0 conflicts
0x5273be82…485e
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
1 conflict on slot 0xf5dc501bf7…748313
Audit this contract →
← previous block·next block →recent activity