← previous blocknext block →recent activity
Analyzing
Block #101,663,906
11 transactions · 11 stateful · 2026-09-03 16:36:48 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,663,906 · 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
5w07w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf681d8fd…c0bd
0x8964d7…10f8
4 touches
1 conflict
0x74d211b2…7044
0x8964d7…10f8
4 touches
1 conflict
0xf681d8fd…c0b7
0x8964d7…10f8
4 touches
1 conflict
0xf681d8fd…c0b8
0x8964d7…10f8
4 touches
1 conflict
0xf681d8fd…c0bb
0x8964d7…10f8
4 touches
1 conflict
0xf681d8fd…c0bc
0x8964d7…10f8
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa86161b5…7e69
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 0xf681d8fdba…b1c0bd
Audit this contract →
← previous block·next block →recent activity