← previous blocknext block →recent activity
Analyzing
Block #99,098,387
16 transactions · 16 stateful · 2026-08-25 17:08:16 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,098,387 · 16 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
5w08w111w012w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x8876d94c…8435
0x2a68ba…90c5
4 touches
1 conflict
0x7dd6bc1c…44dc
0x065c9d…c394
3 touches
1 conflict
0x88f0dbc7…4b13
0xa6afd3…d132
3 touches
1 conflict
0x8c49c85c…ee96
0x34b655…2a6f
2 touches
0 conflicts
0x91ee3bb1…a20d
0x34b655…2a6f
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 0x629109215a…273016
Audit this contract →
← previous block·next block →recent activity