← previous blocknext block →recent activity
Analyzing
Block #106,336,923
21 transactions · 17 stateful · 2026-09-20 01:52:43 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,336,923 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w27w08w116w017w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3e810db…c3e8
0x5be4ee…673f
7 touches
6 conflicts
0xc3e810db…c3f6
0x5be4ee…673f
7 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xb90556e3…0e6a
0x34b655…2a6f
4 touches
1 conflict
0x46279ae7…20dd
0x34ae4d…3fc5
2 touches
0 conflicts
0x53e50026…6d8c
0x34ae4d…3fc5
2 touches
0 conflicts
0x7f4a8466…f2cc
0x34ae4d…3fc5
2 touches
0 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: 0x5be4ee8b…b7673f
6 conflicts on slot 0xc3e810db9b…6ac3e8
Audit this contract →
← previous block·next block →recent activity