← previous blocknext block →recent activity
Analyzing
Block #99,290,683
25 transactions · 22 stateful · 2026-08-26 09:15:53 UTC
Parallelism
84/100
Blocked
27%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,290,683 · 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
5w08w09w010w113w015w216w320w021w122w223w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85c42e7e…1a23
0x77d53b…8080
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7e32f1e0…5612
0x77d53b…8080
6 touches
3 conflicts
0x0fd2cbc5…476b
0x77d53b…8080
6 touches
3 conflicts
0xe3abe489…ebf3
0x77d53b…8080
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824cf63…7ced
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
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: 0x77d53b3b…378080
3 conflicts on slot 0x85c42e7ebd…351a23
Audit this contract →
← previous block·next block →recent activity