← previous blocknext block →recent activity
Analyzing
Block #99,353,230
19 transactions · 17 stateful · 2026-08-26 14:30:33 UTC
Parallelism
89/100
Blocked
18%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,353,230 · 19 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
4w05w19w011w113w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef29686d…b3eb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x44000a8f…8fca
0x851145…3f07
4 touches
1 conflict
0x4c876cb8…bb49
0x851145…3f07
4 touches
1 conflict
0xd689a6a5…0d01
0x34b655…2a6f
4 touches
1 conflict
0xb365f7b4…b89f
0xd32edf…ff58
3 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
2 touches
0 conflicts
0x92385428…6941
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 0xef29686d5b…c4b3eb
Audit this contract →
← previous block·next block →recent activity