← previous blocknext block →recent activity
Analyzing
Block #99,659,510
22 transactions · 20 stateful · 2026-08-27 16:19:50 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.73
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,659,510 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w17w28w39w413w514w115w219w020w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xbdc4532a…8b52
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7dd11fd7…3473
0x34b655…2a6f
4 touches
1 conflict
0xaa1a51de…f226
0x34b655…2a6f
4 touches
1 conflict
0xb4ef3de6…b91c
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: Perpl
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity