← previous blocknext block →recent activity
Analyzing
Block #105,683,063
21 transactions · 20 stateful · 2026-09-17 18:59:28 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,683,063 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w08w111w213w114w315w416w519w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb5b61a2…b2bc
0x34b655…2a6f
12 touches
15 conflicts
0x2693f23b…4da0
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x70e677f5…e3bd
0x34b655…2a6f
6 touches
3 conflicts
0xa8590d68…d5c8
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xa9af9157…5a6e
0x34b655…2a6f
4 touches
1 conflict
0x87ef728f…d3b8
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
15 conflicts on slot 0xeb5b61a29c…4fb2bc
Audit this contract →
← previous block·next block →recent activity