← previous blocknext block →recent activity
Analyzing
Block #106,370,944
24 transactions · 24 stateful · 2026-09-20 04:43:57 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,370,944 · 24 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
2w03w09w010w111w216w317w118w419w520w621w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5229ae5f…473c
0x34b655…2a6f
12 touches
15 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
6 touches
3 conflicts
0x5d1ac445…5233
0x34b655…2a6f
6 touches
3 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
4 touches
1 conflict
0x47a6a8f8…db5c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
15 conflicts on slot 0x5229ae5fa3…b6473c
Audit this contract →
← previous block·next block →recent activity