← previous blocknext block →recent activity
Analyzing
Block #106,934,710
22 transactions · 22 stateful · 2026-09-22 04:02:26 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,934,710 · 22 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
1w02w15w06w08w19w010w011w112w213w314w415w516w618w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8590b692…b267
0x34b655…2a6f
14 touches
21 conflicts
0x7ca519d1…4f93
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
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 0x8590b69238…6ab267
Audit this contract →
← previous block·next block →recent activity