← previous blocknext block →recent activity
Analyzing
Block #101,314,485
28 transactions · 26 stateful · 2026-09-02 11:18:45 UTC
Parallelism
89/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,314,485 · 28 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
1w03w04w05w18w09w111w212w113w220w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xc7425168…d14a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xff324643…41db
0x34b655…2a6f
4 touches
1 conflict
0xa7a7e70b…3afb
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: 0xf5b5f7f8…a36d70
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity