← previous blocknext block →recent activity
Analyzing
Block #100,117,583
11 transactions · 11 stateful · 2026-08-29 06:52:20 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,117,583 · 11 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
1w03w16w07w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbeee2daf…d7e3
0x8964d7…10f8
4 touches
1 conflict
0x0ad69505…af82
0x34b655…2a6f
4 touches
1 conflict
0xbeee2daf…d7e0
0x8964d7…10f8
4 touches
1 conflict
0xbeee2daf…d7e1
0x8964d7…10f8
4 touches
1 conflict
0x258fcaf5…2084
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9b976680…6533
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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: 0x8964d7c9…5b10f8
1 conflict on slot 0xbeee2daf08…f7d7e3
Audit this contract →
← previous block·next block →recent activity