← previous blocknext block →recent activity
Analyzing
Block #100,125,393
11 transactions · 11 stateful · 2026-08-29 07:31:39 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,125,393 · 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
6w07w18w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5b2d0c4…df33
0x8964d7…10f8
4 touches
1 conflict
0x2a4f0eab…e293
0x8964d7…10f8
4 touches
1 conflict
0x2a4f0eab…e294
0x8964d7…10f8
4 touches
1 conflict
0x2a4f0eab…e296
0x8964d7…10f8
4 touches
1 conflict
0xf5b2d0c4…df30
0x8964d7…10f8
4 touches
1 conflict
0xf5b2d0c4…df31
0x8964d7…10f8
4 touches
1 conflict
0x1408a100…f721
0x34b655…2a6f
4 touches
1 conflict
0x6415c9bf…6c16
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 0xf5b2d0c485…83df33
Audit this contract →
← previous block·next block →recent activity