← previous blocknext block →recent activity
Analyzing
Block #99,085,545
17 transactions · 14 stateful · 2026-08-25 16:03:33 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,085,545 · 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
1w05w06w18w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x491c5da4…7163
0x065c9d…c394
2 touches
0 conflicts
0x5217bc5f…3f6a
0x065c9d…c394
2 touches
0 conflicts
0x9054c0e9…6022
0x065c9d…c394
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 0xc3baa205b9…b3f26e
Audit this contract →
← previous block·next block →recent activity