← previous blocknext block →recent activity
Analyzing
Block #106,923,619
37 transactions · 37 stateful · 2026-09-22 03:06:37 UTC
Parallelism
62/100
Blocked
73%
Avg conflicts / tx
2.54
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,923,619 · 37 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w08w19w210w311w412w513w614w717w118w819w920w1021w1122w1223w1332w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53ca1284…cb2c
0x34b655…2a6f
18 touches
36 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
16 touches
28 conflicts
0x42522e76…2592
0x34b655…2a6f
16 touches
28 conflicts
0x8f4be1ed…2e29
0x34b655…2a6f
16 touches
28 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
14 touches
21 conflicts
0x1c0bf87d…7fae
0x34b655…2a6f
14 touches
21 conflicts
0x85bfd0af…ce96
0x34b655…2a6f
12 touches
15 conflicts
0xc7cbc5e5…e7d7
0x34b655…2a6f
10 touches
10 conflicts
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
36 conflicts on slot 0x53ca128412…cacb2c
Audit this contract →
← previous block·next block →recent activity