← previous blocknext block →recent activity
Analyzing
Block #101,067,908
13 transactions · 11 stateful · 2026-09-01 14:38:07 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,067,908 · 13 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
1w08w09w110w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x950358c1…747f
0x8964d7…10f8
4 touches
1 conflict
0x2f643f9a…302c
0x8964d7…10f8
4 touches
1 conflict
0x2f643f9a…302f
0x8964d7…10f8
4 touches
1 conflict
0x2f643f9a…3030
0x8964d7…10f8
4 touches
1 conflict
0x950358c1…747c
0x8964d7…10f8
4 touches
1 conflict
0x950358c1…747d
0x8964d7…10f8
4 touches
1 conflict
0x0e18d182…0425
0x34b655…2a6f
4 touches
1 conflict
0x55192654…91fe
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 0x950358c100…9c747f
Audit this contract →
← previous block·next block →recent activity