← previous blocknext block →recent activity
Analyzing
Block #101,680,971
20 transactions · 19 stateful · 2026-09-03 18:02:39 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
1.15
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,680,971 · 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
1w02w15w06w17w28w39w110w313w214w016w317w419w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6823c28e…594c
0x34b655…2a6f
8 touches
6 conflicts
0xf7772b49…fc12
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x2a2896a0…2a0a
0x34b655…2a6f
8 touches
6 conflicts
0x6c7c1a4b…5751
0x34b655…2a6f
8 touches
6 conflicts
0xa62eb46f…89b1
0x34b655…2a6f
6 touches
3 conflicts
0x4babcbd0…e24c
0x34b655…2a6f
6 touches
3 conflicts
0x4f3cc09a…2804
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
6 conflicts on slot 0x6823c28eb2…d0594c
Audit this contract →
← previous block·next block →recent activity