← previous blocknext block →recent activity
Analyzing
Block #99,184,431
25 transactions · 20 stateful · 2026-08-26 00:21:14 UTC
Parallelism
84/100
Blocked
30%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,184,431 · 25 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
5w07w18w111w215w018w319w123w024w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x248ec32d…b237
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x742436a7…c4d4
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x65021fef…b735
0xa6afd3…d132
4 touches
1 conflict
0x731fd6bb…61ac
0x34b655…2a6f
4 touches
1 conflict
0x8311570f…5321
0x34b655…2a6f
4 touches
1 conflict
0x9482a067…eba9
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
3 conflicts on slot 0x248ec32d87…b4b237
Audit this contract →
← previous block·next block →recent activity