← previous blocknext block →recent activity
Analyzing
Block #100,266,999
16 transactions · 15 stateful · 2026-08-29 19:25:59 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,266,999 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w29w210w312w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7b7b345…1d04
0x34b655…2a6f
8 touches
6 conflicts
0x6caf33e2…c261
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x289ce6b2…d0ae
0x34b655…2a6f
4 touches
1 conflict
0x51087f5a…61f7
0x34b655…2a6f
4 touches
1 conflict
0x831f75b4…945d
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
6 conflicts on slot 0xc7b7b345d0…bc1d04
Audit this contract →
← previous block·next block →recent activity