← previous blocknext block →recent activity
Analyzing
Block #99,110,216
13 transactions · 13 stateful · 2026-08-25 18:07:46 UTC
Parallelism
85/100
Blocked
15%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,110,216 · 13 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
1w03w18w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x757dd9d2…0fb5
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x454247d3…296d
0x34b655…2a6f
4 touches
1 conflict
0xed4cf5a9…f734
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x3cb7ee74…b8a5
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
1 conflict on slot 0x757dd9d2ec…f60fb5
Audit this contract →
← previous block·next block →recent activity