← previous blocknext block →recent activity
Analyzing
Block #105,461,942
23 transactions · 21 stateful · 2026-09-17 00:26:31 UTC
Parallelism
74/100
Blocked
57%
Avg conflicts / tx
1.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,461,942 · 23 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
1w02w13w05w06w111w112w013w114w215w316w417w519w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
10 touches
10 conflicts
0x8ed2a645…b3ce
0x34b655…2a6f
10 touches
10 conflicts
0x213b816c…a5e0
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x9ffdfcdf…866c
0x34b655…2a6f
8 touches
6 conflicts
0x33761f7c…8f85
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity