← previous blocknext block →recent activity
Analyzing
Block #105,617,307
54 transactions · 43 stateful · 2026-09-17 13:28:27 UTC
Parallelism
72/100
Blocked
67%
Avg conflicts / tx
1.93
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #105,617,307 · 54 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w27w08w19w210w311w412w513w614w715w840w341w242w443w544w952w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf48fa71e…bb52
0x34b655…2a6f
22 touches
55 conflicts
0xc7954a60…d294
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x0c7103bd…4f89
0x34b655…2a6f
10 touches
10 conflicts
0x35b0198e…3e0d
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x54e710f5…37ff
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 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
55 conflicts on slot 0xf48fa71eee…43bb52
Audit this contract →
← previous block·next block →recent activity