← previous blocknext block →recent activity
Analyzing
Block #100,136,863
14 transactions · 14 stateful · 2026-08-29 08:29:32 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,136,863 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w010w011w112w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cbde737…7fe8
0x8964d7…10f8
6 touches
3 conflicts
0x8d3d4a4c…7b02
0x8964d7…10f8
6 touches
3 conflicts
0x8d3d4a4c…7b03
0x8964d7…10f8
6 touches
3 conflicts
0x8d3d4a4c…7b06
0x8964d7…10f8
6 touches
3 conflicts
0x8d3d4a4c…7b07
0x8964d7…10f8
6 touches
3 conflicts
0x8d3d4a4c…7b09
0x8964d7…10f8
6 touches
3 conflicts
0x0cbde737…7fe5
0x8964d7…10f8
6 touches
3 conflicts
0x0cbde737…7fe6
0x8964d7…10f8
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: 0x8964d7c9…5b10f8
3 conflicts on slot 0x0cbde737de…577fe8
Audit this contract →
← previous block·next block →recent activity