← previous blocknext block →recent activity
Analyzing
Block #101,817,739
26 transactions · 26 stateful · 2026-09-04 05:30:33 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
1.58
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #101,817,739 · 26 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w28w39w310w413w520w621w122w723w824w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
8 touches
6 conflicts
0xa1e20c62…7c50
0x34b655…2a6f
6 touches
3 conflicts
0x4089d428…b018
0x34b655…2a6f
6 touches
3 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
6 touches
3 conflicts
0x63bed776…8d4a
0x34b655…2a6f
6 touches
3 conflicts
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity