← previous blocknext block →recent activity
Analyzing
Block #99,283,176
16 transactions · 16 stateful · 2026-08-26 08:38:08 UTC
Parallelism
81/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,283,176 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w19w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cf4e036…7a52
0x34b655…2a6f
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x8e10d0a2…b93b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfc8d572c…b27d
0x34b655…2a6f
4 touches
1 conflict
0x12311a9c…d2cc
0x91b81b…6d56
2 touches
0 conflicts
0x861416d1…bc02
0x91b81b…6d56
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 0x5cf4e0368f…c07a52
Audit this contract →
← previous block·next block →recent activity