← previous blocknext block →recent activity
Analyzing
Block #100,615,011
20 transactions · 18 stateful · 2026-08-31 00:39:12 UTC
Parallelism
90/100
Blocked
33%
Avg conflicts / tx
0.35
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,615,011 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w06w19w010w111w012w114w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2d9f3c3…055b
0x928dc8…8207
4 touches
1 conflict
0x6ede85f4…0b8a
0x928dc8…8207
4 touches
1 conflict
0x6ede85f4…0b8b
0x928dc8…8207
4 touches
1 conflict
0x8dca7cdd…b416
0x928dc8…8207
4 touches
1 conflict
0x8dca7cdd…b418
0x928dc8…8207
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x29cd05f5…390c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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: 0x928dc8af…fd8207
1 conflict on slot 0xe2d9f3c30e…c1055b
Audit this contract →
← previous block·next block →recent activity