← previous blocknext block →recent activity
Analyzing
Block #101,938,377
20 transactions · 19 stateful · 2026-09-04 15:39:27 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,938,377 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w06w18w09w111w112w213w314w418w019w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d6d36e9…9fb4
0x34b655…2a6f
10 touches
10 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3e3f27ce…580c
0x34b655…2a6f
6 touches
3 conflicts
0xeb1b66a1…ce4e
0x34b655…2a6f
6 touches
3 conflicts
0x56e0d685…c960
0x34b655…2a6f
6 touches
3 conflicts
0x76a639da…08f7
0x34b655…2a6f
4 touches
1 conflict
0x93aaefce…5be5
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
10 conflicts on slot 0x6d6d36e95c…459fb4
Audit this contract →
← previous block·next block →recent activity