← previous blocknext block →recent activity
Analyzing
Block #101,666,203
13 transactions · 11 stateful · 2026-09-03 16:48:21 UTC
Parallelism
62/100
Blocked
45%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,666,203 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w37w411w012w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x230b0b56…a675
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xeceefd39…ef67
0x34b655…2a6f
4 touches
1 conflict
0x05e25943…dd95
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x70f836c8…cf6d
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
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: Perpl
3 conflicts on slot 0x230b0b56f7…65a675
Audit this contract →
← previous block·next block →recent activity