← previous blocknext block →recent activity
Analyzing
Block #101,815,796
11 transactions · 11 stateful · 2026-09-04 05:20:46 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,815,796 · 11 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
2w03w14w15w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaea4b94…0aea
0x34b655…2a6f
6 touches
3 conflicts
0xd98afa6e…3364
0x34b655…2a6f
4 touches
1 conflict
0x1a5b575c…10dc
0x34b655…2a6f
4 touches
1 conflict
0x3cb45e6c…97c0
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x4dffc33e…068d
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x8a26dd8e…c940
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: Perpl
3 conflicts on slot 0xfaea4b9439…210aea
Audit this contract →
← previous block·next block →recent activity