← previous blocknext block →recent activity
Analyzing
Block #105,748,805
23 transactions · 21 stateful · 2026-09-18 00:30:20 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,748,805 · 23 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
1w02w13w06w09w110w213w015w118w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b4cc9c9…dca4
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0xdd084cf8…1a71
0x99c7a7…8bf0
4 touches
1 conflict
0x213b816c…a5e0
0x34b655…2a6f
4 touches
1 conflict
0x33649c4f…b327
0x34b655…2a6f
4 touches
1 conflict
0xf6b6409a…7a4f
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
3 conflicts on slot 0x2b4cc9c9fe…fcdca4
Audit this contract →
← previous block·next block →recent activity