← previous blocknext block →recent activity
Analyzing
Block #101,973,995
20 transactions · 20 stateful · 2026-09-04 18:40:00 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,973,995 · 20 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
1w02w13w04w15w06w17w28w310w114w015w116w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04d4f30d…4dfb
0x34b655…2a6f
8 touches
6 conflicts
0xfd713bab…a651
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xeb1b66a1…ce4e
0x34b655…2a6f
8 touches
6 conflicts
0xc52785b9…08f8
0x34b655…2a6f
8 touches
6 conflicts
0x56e0d685…c960
0x34b655…2a6f
8 touches
6 conflicts
0x5746581b…0cb1
0x34b655…2a6f
8 touches
6 conflicts
0xe6875750…9542
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 0x04d4f30d9e…3b4dfb
Audit this contract →
← previous block·next block →recent activity