← previous blocknext block →recent activity
Analyzing
Block #105,845,438
15 transactions · 15 stateful · 2026-09-18 08:38:07 UTC
Parallelism
47/100
Blocked
47%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,845,438 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w17w28w39w410w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x904bb1d5…0100
0x34b655…2a6f
10 touches
10 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
6 touches
3 conflicts
0xd1448207…452d
0x34b655…2a6f
6 touches
3 conflicts
0xbbdfd584…ab2f
0x34b655…2a6f
6 touches
3 conflicts
0x941bd594…21fd
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity