← previous blocknext block →recent activity
Analyzing
Block #101,967,179
13 transactions · 10 stateful · 2026-09-04 18:05:30 UTC
Parallelism
54/100
Blocked
50%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,967,179 · 13 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
1w02w03w14w26w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ab70ccd…2683
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x5746581b…0cb1
0x34b655…2a6f
6 touches
3 conflicts
0x6c7c1a4b…5751
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xa62eb46f…89b1
0x34b655…2a6f
6 touches
3 conflicts
0xb40e601f…bf98
0x34b655…2a6f
6 touches
3 conflicts
0x04d4f30d…4dfb
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
3 conflicts on slot 0x4ab70ccdf8…612683
Audit this contract →
← previous block·next block →recent activity