← previous blocknext block →recent activity
Analyzing
Block #101,988,424
20 transactions · 17 stateful · 2026-09-04 19:53:14 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,988,424 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w211w112w214w215w318w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5da92df7…74b5
0x34b655…2a6f
6 touches
3 conflicts
0xc852b267…9d14
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7caab345…9635
0x34b655…2a6f
6 touches
3 conflicts
0x5890dedf…54c9
0x34b655…2a6f
4 touches
1 conflict
0x6823c28e…594c
0x34b655…2a6f
4 touches
1 conflict
0x6c7c1a4b…5751
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
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 0x5da92df7bf…9274b5
Audit this contract →
← previous block·next block →recent activity