← previous blocknext block →recent activity
Analyzing
Block #100,870,266
16 transactions · 16 stateful · 2026-08-31 22:03:38 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,870,266 · 16 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
1w02w13w14w05w08w29w010w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0xf00adc3b…2f51
0x065c9d…c394
6 touches
3 conflicts
0xe2986832…1667
0x33a247…6221
4 touches
1 conflict
0x1d9154e7…8821
0x34b655…2a6f
4 touches
1 conflict
0x820d7282…6c34
0x34b655…2a6f
4 touches
1 conflict
0x4d1e3e31…edf8
0x3bd359…433a
4 touches
1 conflict
0x997ccc40…4dfd
0x3bd359…433a
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: 0xf5b5f7f8…a36d70
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity