← previous blocknext block →recent activity
Analyzing
Block #99,879,154
23 transactions · 23 stateful · 2026-08-28 10:51:28 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,879,154 · 23 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
2w03w05w06w07w18w211w012w013w115w116w117w219w320w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x08db2444…22b2
0x34b655…2a6f
6 touches
3 conflicts
0xf4a97154…2d71
0x34b655…2a6f
6 touches
3 conflicts
0x75f36d60…8556
0x34b655…2a6f
6 touches
3 conflicts
0xbd590df7…9891
0x34b655…2a6f
6 touches
3 conflicts
0xc16e646d…4fb0
0x34b655…2a6f
6 touches
3 conflicts
0xee9cd753…6410
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity