← previous blocknext block →recent activity
Analyzing
Block #106,924,254
26 transactions · 24 stateful · 2026-09-22 03:09:49 UTC
Parallelism
58/100
Blocked
50%
Avg conflicts / tx
1.5
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,924,254 · 26 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w09w110w211w312w413w514w615w716w817w918w1024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574628e9…dcc3
0x34b655…2a6f
16 touches
28 conflicts
0xc7b7704f…ab36
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0xd192f4ed…d7ec
0x34b655…2a6f
10 touches
10 conflicts
0x4ff73652…74f7
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xc137f51f…cd2e
0x851145…3f07
4 touches
1 conflict
0x469dac8d…3411
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: Perpl
28 conflicts on slot 0x574628e919…e4dcc3
Audit this contract →
← previous block·next block →recent activity