← previous blocknext block →recent activity
Analyzing
Block #100,561,273
9 transactions · 9 stateful · 2026-08-30 20:08:52 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,561,273 · 9 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
3w04w15w26w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75f26c4f…b364
0x8964d7…10f8
4 touches
1 conflict
0x65732663…3bbf
0x8964d7…10f8
4 touches
1 conflict
0x65732663…3bc0
0x8964d7…10f8
4 touches
1 conflict
0x65732663…3bc3
0x8964d7…10f8
4 touches
1 conflict
0x65732663…3bc4
0x8964d7…10f8
4 touches
1 conflict
0x65732663…3bc6
0x8964d7…10f8
4 touches
1 conflict
0x75f26c4f…b361
0x8964d7…10f8
4 touches
1 conflict
0x75f26c4f…b362
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 0x75f26c4fce…06b364
Audit this contract →
← previous block·next block →recent activity