← previous blocknext block →recent activity
Analyzing
Block #99,983,134
25 transactions · 22 stateful · 2026-08-28 19:35:24 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,983,134 · 25 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
3w05w06w19w115w016w217w118w019w121w223w024w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x17e28ddf…ce0d
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x65021fef…b735
0xa6afd3…d132
4 touches
1 conflict
0x71717491…10cf
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
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: 0xf5b5f7f8…a36d70
1 conflict on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity