← previous blocknext block →recent activity
Analyzing
Block #99,987,820
17 transactions · 17 stateful · 2026-08-28 19:59:04 UTC
Parallelism
88/100
Blocked
24%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,987,820 · 17 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
1w06w07w19w010w112w013w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xceb8568b…f513
0x8964d7…10f8
4 touches
1 conflict
0xceb8568b…f50d
0x8964d7…10f8
4 touches
1 conflict
0xceb8568b…f50e
0x8964d7…10f8
4 touches
1 conflict
0xceb8568b…f511
0x8964d7…10f8
4 touches
1 conflict
0xceb8568b…f512
0x8964d7…10f8
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x627738d1…db02
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: 0x8964d7c9…5b10f8
1 conflict on slot 0xceb8568b82…eef513
Audit this contract →
← previous block·next block →recent activity