← previous blocknext block →recent activity
Analyzing
Block #101,967,869
21 transactions · 18 stateful · 2026-09-04 18:08:58 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,967,869 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w19w010w011w216w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x179b31b3…6dd2
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x3d408a46…8a53
0x34b655…2a6f
6 touches
3 conflicts
0x76e02d19…7609
0x34b655…2a6f
4 touches
1 conflict
0x839d77a9…9a51
0x34b655…2a6f
4 touches
1 conflict
0xbc8fb280…76a3
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity