← previous blocknext block →recent activity
Analyzing
Block #100,122,071
13 transactions · 13 stateful · 2026-08-29 07:14:56 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,122,071 · 13 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
9w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x301d0a8f…e1f7
0x8964d7…10f8
4 touches
1 conflict
0x301d0a8f…e1f8
0x8964d7…10f8
4 touches
1 conflict
0x301d0a8f…e1fb
0x8964d7…10f8
4 touches
1 conflict
0x301d0a8f…e1fc
0x8964d7…10f8
4 touches
1 conflict
0x301d0a8f…e1fd
0x8964d7…10f8
4 touches
1 conflict
0x632d9618…962a
0x8964d7…10f8
4 touches
1 conflict
0x632d9618…962b
0x8964d7…10f8
4 touches
1 conflict
0x632d9618…962d
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 0x301d0a8fca…32e1f7
Audit this contract →
← previous block·next block →recent activity