← previous blocknext block →recent activity
Analyzing
Block #99,586,891
14 transactions · 14 stateful · 2026-08-27 10:09:58 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,586,891 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w110w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2caeb7f5…b6bb
0x34b655…2a6f
6 touches
3 conflicts
0xb64b9585…6270
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xbe6835a1…a184
0x34b655…2a6f
4 touches
1 conflict
0xddc5beb2…3f56
0x34b655…2a6f
4 touches
1 conflict
0x0db07ef0…b141
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
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 0x2caeb7f5e5…18b6bb
Audit this contract →
← previous block·next block →recent activity