← previous blocknext block →recent activity
Analyzing
Block #106,534,919
23 transactions · 23 stateful · 2026-09-20 18:29:15 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,534,919 · 23 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
1w02w03w18w19w010w211w113w114w315w417w518w622w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9ddc6d5…86a2
0x34b655…2a6f
14 touches
21 conflicts
0xac0b4a08…faae
0x34b655…2a6f
8 touches
6 conflicts
0xd62f3741…b903
0x34b655…2a6f
8 touches
6 conflicts
0xe283e878…7262
0x34b655…2a6f
8 touches
6 conflicts
0x69411fb3…e36d
0x34b655…2a6f
6 touches
3 conflicts
0x172b0de5…980b
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x9a74ca82…17d1
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
21 conflicts on slot 0xd9ddc6d597…8d86a2
Audit this contract →
← previous block·next block →recent activity