← previous blocknext block →recent activity
Analyzing
Block #101,682,169
14 transactions · 13 stateful · 2026-09-03 18:08:41 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,682,169 · 14 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
2w03w14w05w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd11cefaa…d26f
0x8964d7…10f8
4 touches
1 conflict
0x99b95896…a8ff
0x8964d7…10f8
4 touches
1 conflict
0x99b95896…a900
0x8964d7…10f8
4 touches
1 conflict
0x99b95896…a902
0x8964d7…10f8
4 touches
1 conflict
0xd11cefaa…d268
0x8964d7…10f8
4 touches
1 conflict
0xd11cefaa…d269
0x8964d7…10f8
4 touches
1 conflict
0xd11cefaa…d26c
0x8964d7…10f8
4 touches
1 conflict
0xd11cefaa…d26d
0x8964d7…10f8
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 0xd11cefaa26…81d26f
Audit this contract →
← previous block·next block →recent activity