← previous blocknext block →recent activity
Analyzing
Block #101,955,263
20 transactions · 16 stateful · 2026-09-04 17:05:06 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,955,263 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w17w08w112w313w414w515w618w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xeb4304a5…dd06
0x34b655…2a6f
6 touches
3 conflicts
0xfcd7574f…a3a2
0x34b655…2a6f
6 touches
3 conflicts
0x54fe7e99…7139
0x34b655…2a6f
6 touches
3 conflicts
0xa7e3ddfa…f0c7
0x34b655…2a6f
6 touches
3 conflicts
0x01315072…0e2d
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 0x045532dd4b…244b7d
Audit this contract →
← previous block·next block →recent activity