← previous blocknext block →recent activity
Analyzing
Block #105,606,224
26 transactions · 23 stateful · 2026-09-17 12:32:39 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,606,224 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w18w010w011w112w113w218w219w121w022w123w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x1a79e9de…99e6
0x851145…3f07
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x18978822…2623
0x34b655…2a6f
4 touches
1 conflict
0x273d7e4b…be3c
0x34b655…2a6f
4 touches
1 conflict
0x3a08dbb9…8750
0x34b655…2a6f
4 touches
1 conflict
0xb6ed511f…6b68
0x34b655…2a6f
4 touches
1 conflict
0xc10b903d…2f54
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: 0x80c74517…647210
3 conflicts on slot 0x0000000000…00004c
Audit this contract →
← previous block·next block →recent activity