← previous blocknext block →recent activity
Analyzing
Block #105,849,919
19 transactions · 16 stateful · 2026-09-18 09:00:39 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,849,919 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w19w211w312w413w014w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23529e13…6f25
0x34b655…2a6f
10 touches
10 conflicts
0x5e4ed8fb…2d93
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
8 touches
6 conflicts
0xc10b903d…2f54
0x34b655…2a6f
6 touches
3 conflicts
0xb11d0fc9…04f6
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x0f94e353…1f32
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
10 conflicts on slot 0x23529e136b…8a6f25
Audit this contract →
← previous block·next block →recent activity