← previous blocknext block →recent activity
Analyzing
Block #101,893,570
23 transactions · 20 stateful · 2026-09-04 11:52:07 UTC
Parallelism
87/100
Blocked
40%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,893,570 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w08w011w113w114w115w217w018w120w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6df1d50f…8a92
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd6d0e119…6a6a
0x99c7a7…8bf0
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x8226c92c…ece7
0x754704…b603
4 touches
1 conflict
0xe4940a46…26a0
0x754704…b603
4 touches
1 conflict
0xfe992cec…eaaa
0x754704…b603
4 touches
1 conflict
0x3b9910a2…6177
0x99c7a7…8bf0
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 0x6df1d50f92…968a92
Audit this contract →
← previous block·next block →recent activity