← previous blocknext block →recent activity
Analyzing
Block #105,845,055
29 transactions · 26 stateful · 2026-09-18 08:36:09 UTC
Parallelism
76/100
Blocked
62%
Avg conflicts / tx
1.55
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,845,055 · 29 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
1w02w13w24w35w46w59w117w219w320w421w522w627w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6d40b7f…2969
0x34b655…2a6f
14 touches
21 conflicts
0xe566e4e7…af2c
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x14d1bf0e…e0a0
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001f
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002f
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 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
21 conflicts on slot 0xa6d40b7f0d…ff2969
Audit this contract →
← previous block·next block →recent activity