← previous blocknext block →recent activity
Analyzing
Block #101,938,044
14 transactions · 14 stateful · 2026-09-04 15:37:43 UTC
Parallelism
57/100
Blocked
36%
Avg conflicts / tx
1.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,938,044 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w210w011w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb75367ff…a2b7
0x34b655…2a6f
12 touches
15 conflicts
0x51fc8795…126f
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7dd96c96…7335
0x34b655…2a6f
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
6 touches
3 conflicts
0xa4999434…0d29
0x34b655…2a6f
5 touches
3 conflicts
0x93aaefce…5be5
0x34b655…2a6f
4 touches
1 conflict
0x987859be…2686
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
15 conflicts on slot 0xb75367ffdb…6fa2b7
Audit this contract →
← previous block·next block →recent activity