← previous blocknext block →recent activity
Analyzing
Block #101,954,780
19 transactions · 19 stateful · 2026-09-04 17:02:39 UTC
Parallelism
58/100
Blocked
53%
Avg conflicts / tx
1.74
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,954,780 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w16w27w38w39w410w511w612w717w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0x00500a94…20d5
0x34b655…2a6f
6 touches
3 conflicts
0x2a3f40b6…e39c
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc7aaba31…b5f9
0x34b655…2a6f
4 touches
1 conflict
0xffdc4ab0…9626
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
28 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity